Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for ISTIO sidecar #354

Closed
wants to merge 14 commits into from

Conversation

jeenadeepak
Copy link

What was changed

Add support for ISTIO deployment

Why?

Istio run with each pod due to which one time job/pod are not successfully terminal, istio is not required here as db schema setup and update are one time job, hence skipping istio for jobs.

Checklist

  1. Closes
    #[Bug] Temporal services are not starting when deployed in istio enabled namespace #353

  2. How was this tested:

Testing on AWS EKS with istio.

  1. Any docs updates needed?

no

EC2 Default User and others added 3 commits January 29, 2023 12:59
Istio run with each pod due to which one time job/pod are not successfully terminal, istio is not required here as these are one time job, hence skipping istio for one time job,
@jeenadeepak jeenadeepak requested review from a team as code owners January 29, 2023 17:15
@CLAassistant
Copy link

CLAassistant commented Jan 29, 2023

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ jeenadeepak
❌ EC2 Default User


EC2 Default User seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

@mindaugasrukas mindaugasrukas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make these optional via extraAnnotations value.
As an example, see https://github.com/temporalio/helm-charts/blob/master/templates/serviceaccount.yaml#L16.

merging with temporalio-helm-charts
@jeenadeepak
Copy link
Author

@mindaugasrukas : I have checked this example, it does not seems correct solution.

I am facing this issue with DB migration job due to istio, rest service are working fine with istio, so I do not want remove istio for entire application, but as per this example this will skip istio for other temporal services.

There are 2 problem I have identified with DB migration:
1: DB migration is one time job, hence db migration container quit but istio container is log running so it showing error,
2: DB migration started before istio networking hence it stop DB migration container to connect with SQL port.

@mindaugasrukas
Copy link
Contributor

My point is that this change will add environment-specific fields to the generic template. We don't want to add every environment-specific setting to the template but have the ability to inject user-specific configs. So, I'd like to ask you to make the template change, allowing you or anyone else to inject their needs.

@underrun
Copy link
Contributor

to be more specific - you can change this template here: https://github.com/temporalio/helm-charts/blob/master/templates/server-job.yaml#L15

to add something like

    {{- with .Values.serviceAccount.extraAnnotations }}
      {{- toYaml . | nindent 4 }}
    {{- end }}

but where you change serviceAccount to be for only jobs or something.

@vishwa-trulioo
Copy link

Any update on this?

@jeenadeepak
Copy link
Author

@mindaugasrukas : I have updated template as per your suggestion.

@jeenadeepak jeenadeepak closed this Feb 2, 2024
@jeenadeepak jeenadeepak reopened this Feb 2, 2024
@jeenadeepak jeenadeepak closed this Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants