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

feat(kuma-cp): init container first by default #5857

Merged
merged 3 commits into from
Feb 20, 2023

Conversation

zekth
Copy link
Contributor

@zekth zekth commented Jan 28, 2023

Follow up of #3121 to put the init container as first by default. I might be missing something; happy to work on this if there is other things needed.

Question is do we want to make this operation as an option? So do we create a pod annotation for this?

Checklist prior to review

  • Link to docs PR or issue --
  • Link to UI issue or PR --
  • Is the issue worked on linked? --
  • The PR does not hardcode values that might break projects that depend on kuma (e.g. "kumahq" as a image registry) --
  • The PR will work for both Linux and Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
  • Unit Tests --
  • E2E Tests --
  • Manual Universal Tests --
  • Manual Kubernetes Tests --
  • Do you need to update UPGRADE.md? --
  • Does it need to be backported according to the backporting policy? --
  • Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

@lahabana
Copy link
Contributor

/golden_files

@lahabana
Copy link
Contributor

Question is do we want to make this operation as an option? So do we create a pod annotation for this?

As K8s by default doesn't guarantee anything about startup and order of containers I don't think it's useful to add an annotation to control this. I think the only place we'd add an annotation is for the 2nd part of this work (the one that adds a preStart hook)

@zekth zekth marked this pull request as ready for review February 1, 2023 09:32
@zekth zekth requested review from a team, lobkovilya and lukidzi and removed request for a team February 1, 2023 09:32
@michaelbeaumont michaelbeaumont changed the title fix: init container first by default feat: init container first by default Feb 6, 2023
@lahabana lahabana changed the title feat: init container first by default feat(kuma-cp): init container first by default Feb 6, 2023
@lahabana
Copy link
Contributor

lahabana commented Feb 8, 2023

@lobkovilya or @lukidzi can we get a review/merge on this?

zekth and others added 2 commits February 16, 2023 12:55
Signed-off-by: Vincent Le Goff <vincent.legoff@konghq.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@lahabana lahabana enabled auto-merge (squash) February 16, 2023 17:35
@lahabana lahabana enabled auto-merge (squash) February 16, 2023 17:36
@lahabana lahabana merged commit 6cf9648 into kumahq:master Feb 20, 2023
@zekth zekth deleted the fix/init-container-order branch February 20, 2023 14:32
slonka added a commit that referenced this pull request Apr 14, 2023
slonka added a commit to slonka/kuma that referenced this pull request Apr 14, 2023
slonka added a commit that referenced this pull request Apr 14, 2023
Revert "feat(kuma-cp): init container first by default (#5857)"

This reverts commit 6cf9648.
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.

None yet

3 participants