-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add aws-node-termination-handler, fix test values filenames #954
Conversation
Co-authored-by: Andreas Sommer <[email protected]>
Manual test worked fine |
@@ -0,0 +1,61 @@ | |||
{{/* Default Helm values for the app */}} | |||
{{/* See schema for the appropriate app version here https://github.com/giantswarm/aws-ebs-csi-driver-app/blob/master/helm/aws-ebs-csi-driver-app/values.schema.json */}} |
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.
{{/* See schema for the appropriate app version here https://github.com/giantswarm/aws-ebs-csi-driver-app/blob/master/helm/aws-ebs-csi-driver-app/values.schema.json */}} | |
{{/* See schema for the appropriate app version here https://github.com/giantswarm/aws-node-termination-handler-app/blob/main/helm/aws-node-termination-handler/values.schema.json */}} |
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.
Done but using https://github.com/giantswarm/aws-nth-bundle
cluster-apps-operator.giantswarm.io/watching: "" | ||
{{- include "labels.common" . | nindent 4 }} | ||
spec: | ||
suspend: false # It can be unsuspended by the post-install/post-upgrade hook. Useful if we need to populate some fields later on. |
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.
GROUP: helm.toolkit.fluxcd.io
KIND: HelmRelease
VERSION: v2beta1
FIELD: suspend <boolean>
DESCRIPTION:
Suspend tells the controller to suspend reconciliation for this HelmRelease,
it does not apply to already started reconciliations. Defaults to false.
Being false
the default, I'd remove it from here to avoid adding unnecessary noise.
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.
done (removed)
helm/cluster-aws/values.schema.json
Outdated
"awsNodeTerminationHandler": { | ||
"$ref": "#/$defs/helmRelease", | ||
"type": "object", | ||
"title": "AWS EBS CSI driver", |
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.
"title": "AWS EBS CSI driver", | |
"title": "AWS Node Termination Handler", |
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.
Don't forget this one. Other than that, LGTM
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.
Fixed, but it's not even used in README.md 😆
helm/cluster-aws/values.schema.json
Outdated
@@ -1665,6 +1671,11 @@ | |||
"minLength": 1, | |||
"pattern": "^[-a-zA-Z0-9_\\.]{1,63}$" | |||
}, | |||
"awsPartition": { |
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.
If this is used for local rendering, I was wondering if it would make more sense to put it under the internal
field. It's tricky, because internal
may end up being a "everything fits in here" bucket for different fields, but I guess internal
was added for fields that were supposed to be used by us, not the customer, like this one.
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.
Since cluster-aws has its own internal.*
, I can easily add it there. It won't clash with cluster's cluster.internal.*
values. Done, please check.
There were differences in the rendered Helm template, please check! Output
|
Co-authored-by: paurosello <[email protected]>
What this PR does / why we need it
Towards https://github.com/giantswarm/giantswarm/issues/31843. Backport of #945.
I'm manually testing and then merging this, given that E2E tests currently don't work if a new application gets added (see original PR).
Checklist
Trigger E2E tests
E2E test will fail – same as in original PR.