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: add support for default container annotation (#8015) #9769

Merged
merged 4 commits into from Aug 9, 2022
Merged

feat: add support for default container annotation (#8015) #9769

merged 4 commits into from Aug 9, 2022

Conversation

edwardgronroos
Copy link
Contributor

@edwardgronroos edwardgronroos commented Jun 23, 2022

By using the (kubectl.kubernetes.io/default-container annotation)[https://kubernetes.io/docs/reference/labels-annotations-taints/#kubectl-kubernetes-io-default-container] on a pod, we can let developers decide default, both for argocd and kubectl.

It's particularly useful if/when sidecars decide where to be injected, as mentioned in the issue linkerd recently changed to be the first starting container (linkerd/linkerd2#5967) causing UI to always open up logs on that tab.

Fixes #8015

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).

Signed-off-by: Edward Grönroos <edward@gronroos.se>
Signed-off-by: Edward Grönroos <edward@gronroos.se>
@crenshaw-dev crenshaw-dev changed the title Add support for default container annotation feat: add support for default container annotation (#8015) Jun 23, 2022
@crenshaw-dev
Copy link
Collaborator

@edwardgronroos can you resolve conflicts?

@codecov
Copy link

codecov bot commented Jun 29, 2022

Codecov Report

Merging #9769 (6d457a5) into master (915bd81) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9769   +/-   ##
=======================================
  Coverage   46.18%   46.18%           
=======================================
  Files         226      226           
  Lines       27581    27581           
=======================================
  Hits        12737    12737           
  Misses      13124    13124           
  Partials     1720     1720           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Copy link
Member

@rbreeze rbreeze left a comment

Choose a reason for hiding this comment

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

LGTM

@crenshaw-dev crenshaw-dev merged commit af40d52 into argoproj:master Aug 9, 2022
ashutosh16 pushed a commit to ashutosh16/argo-cd that referenced this pull request Aug 11, 2022
…rgoproj#9769)

* feat: add support for default container in logs/exec

Signed-off-by: Edward Grönroos <edward@gronroos.se>

* chore: resolve linting issues

Signed-off-by: Edward Grönroos <edward@gronroos.se>
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.

Support kubectl.kubernetes.io/default-container annotation
3 participants