-
Notifications
You must be signed in to change notification settings - Fork 591
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(orc8r): K8s Include labels and annotations based on the image/chart being deployed #10085
Conversation
Thanks for opening a PR! 💯 A couple initial guidelines
Howto
More infoPlease take a moment to read through the Magma project's
If this is your first Magma PR, also consider reading
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is still stacked on the previous PR (?). Can you rebase it onto latest master then re-request a review?
f6c3bb7
to
89f9715
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A general comment is to just check if all the pods we deploy are tagged with the image and chart versions as desired.
template: | ||
metadata: | ||
labels: | ||
{{ tuple $envAll "nms" "nginx" | include "nms.selector-labels" | indent 8 }} | ||
{{ include "magmalte-image-version-label" . | indent 8 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use magmalte-image-version-label for nginx-proxy deployment as well? Looking at our artifactory for helm charts, we have one for orc8r and one for lte-orc8r which I presume handles it for the controller and magmalte images respectively. If so, is there a possibility that nginx-proxy and magmalte could have different chart versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use magmalte-image-version-label for nginx-proxy deployment as well
No, I think we should use the nginx-image-version-label
. I corrected the PR to reflect that.
If so, is there a possibility that nginx-proxy and magmalte could have different chart versions?
No, both nginx deployments will use the same helm value configuration.
Being more clear, there are two nginx deployments:
We expect them to have the same image-label value, though the char-version will be different, #1 will receive the NMS sub-chart version, and the #2 will receive Orc8r version.
89f9715
to
eb0d164
Compare
eb0d164
to
0aed2c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes. LGTM.
I remember we had a plan to upgrade the EKS version as well (due to future support for nginx ingress). Is it going in a different PR?
Yes, I included in #10212, which is merged now. Rationale is that PR changes the k8s resources already, made more sense to be there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skimmed, lgtm
…etup Assuming we're not deploying prometheus these configurations will not be needed. In addition if the job fails it will not allow other services to be deployed. Signed-off-by: Joary Paulo Wanzeler Fortuna <joarypl@fb.com>
This applies the same behaviour defined in orc8rlib in templates/_pdb.yaml Signed-off-by: Joary Paulo Wanzeler Fortuna <joarypl@fb.com>
…being deployied Signed-off-by: Joary Paulo Wanzeler Fortuna <joarypl@fb.com>
…c8r charts Also include labels to pods template Signed-off-by: Joary Paulo Wanzeler Fortuna <joarypl@fb.com>
0aed2c3
to
f5116ed
Compare
Summary
In essence the same as #9981, adding two points:
More details:
Also fixed some bugs to allow testing:
Test Plan
A - Check the labels / annotations for each k8s object with helm template:
Result for 'orc8r' helm chart: https://gist.github.com/joary/e7156e6f6fce6834323aaa709925f6b8
Result for 'lte-orc8r' helm chart:
https://gist.github.com/joary/aa3a8bf3974bc5ec9ca98ed35cd57325
B - Check the labels for each pod after deploying both orc8r and lte-orc8r charts
kubectl get pods -n <namespace> --show-labels
:https://gist.github.com/joary/c95906e247634f21f277d85772222c42
Additional Information