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

Ability to disable IRSA role association in route53 scenario #614

Merged
merged 1 commit into from
Sep 9, 2021

Conversation

ytsarev
Copy link
Member

@ytsarev ytsarev commented Sep 9, 2021

Signed-off-by: Yury Tsarev [email protected]

@@ -29,7 +29,7 @@ kind: ServiceAccount
metadata:
name: k8gb-external-dns
namespace: {{ .Release.Namespace }}
{{ if .Values.route53.enabled }}
{{ if and .Values.route53.enabled .Values.route53.irsaRole }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we do this oposite?
{{ if .Values.route53.irsaRole }}

Copy link
Member Author

Choose a reason for hiding this comment

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

how is it the opposite?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Well irsaRole asumes you have route53 is enabled

Copy link
Member Author

Choose a reason for hiding this comment

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

that's exactly the logic I want to convey. if route53 enabled AND irsaRole is specified then inject the annotation. Do you see any problem with this logic?

Copy link
Collaborator

Choose a reason for hiding this comment

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

It is duplicit and hard to read

Copy link
Member Author

Choose a reason for hiding this comment

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

but also not a rocket science and more reliable

Copy link
Member Author

Choose a reason for hiding this comment

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

Also it enables us to keep example at https://github.com/k8gb-io/k8gb/blob/master/chart/k8gb/values.yaml#L68 and not forcing it to false.

Copy link
Member Author

Choose a reason for hiding this comment

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

@k0da also added inline clarification comment please re-review

* Fixes #593
* To disable just set `irsaRole` to `false`

Signed-off-by: Yury Tsarev <[email protected]>
Copy link
Collaborator

@k0da k0da left a comment

Choose a reason for hiding this comment

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

LGTM

@ytsarev ytsarev merged commit 3d613b1 into master Sep 9, 2021
@ytsarev ytsarev deleted the optional-irsa branch September 9, 2021 08:34
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.

Provide K8gb without IRSA Annotation capability
2 participants