-
Notifications
You must be signed in to change notification settings - Fork 809
Template annotations in all major harbor components #2100
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
base: main
Are you sure you want to change the base?
Conversation
206e46b
to
55f2f08
Compare
Hi @nepomucen , Thanks for your contribution to harbor-helm! Could you also help to update the configuration part of the README.md file? Appreciate! |
78528b9
to
532abe1
Compare
Hi @MinerYang Thanks for the code review. The documentation part is now updated too. |
@MinerYang would you be so kind, and re-review my PR with absorbed fixes. |
This PR is being marked stale due to a period of inactivty. If this PR is still relevant, please comment or remove the stale label. Otherwise, this PR will close in 30 days. |
@reasonerjt Could you please take a look at this PR ? I'd appreciate a review. |
Was about to open an issue as to why users cannot adjust annotations on deployments, only on pods, but then found this PR. What is the hold up here? |
@nepomucen btw, would be a good idea to add it to the nginx component. It's the only one left without it. |
I also need this feature to be able to skip some opt-out kyverno policies on my openshift cluster, can this please get some more attention. Being able to set annotations to facilitate cross operability between componentes/tools is a pretty core aspect of helm charts |
Signed-off-by: nepomucen <szymon@aus.krakow.pl>
Signed-off-by: nepomucen <szymon@aus.krakow.pl>
Signed-off-by: nepomucen <szymon@aus.krakow.pl>
Signed-off-by: nepomucen <szymon@aus.krakow.pl>
Signed-off-by: nepomucen <szymon@aus.krakow.pl>
add35f9
to
bd1dafe
Compare
@igcherkaev, thx for suggestion, the last remaining component |
@nepomucen I ended up just forking this repo and adjusting the templates and hosting the chart privately :( P.S. I also had to change logic around storage persistence and gcs-key.json mount. Not sure how persistence.enabled is related to mounting gcs-key.json tbh, but it is what it is right now... |
Manually resolved conflicts in README.md
I merged the 'upstream/main' into my 'add/annotations' branch, and manually resolved conflict. |
What does this change resolve?
Example use case:
Users of stakater/Reloader can now specify
annotations
to the various Harbor components, to letreloader
perform a rolling upgrade on related Deployment's pods whensecret
specified in annotation is updated.Testing