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

[radar-self-enrolment-ui] fix radar SEP ui chart #262

Merged
merged 10 commits into from
Oct 6, 2024
Merged

[radar-self-enrolment-ui] fix radar SEP ui chart #262

merged 10 commits into from
Oct 6, 2024

Conversation

yatharthranjan
Copy link
Member

Description of the change

Fixes a minor issue with the radar self-enrolment UI chart that prevents it from deploying.

Benefits

Possible drawbacks

Applicable issues

Error: release kratos-selfservice-ui-node failed, and has been uninstalled due to atomic being set: failed pre-install: unable to build kubernetes object for deleting hook radar-self-enrolment-ui/templates/secret.yaml: unable to decode "": json: cannot unmarshal number into Go struct field ObjectMeta.metadata.annotations of type string

Additional information

Checklist

  • Chart version bumped in Chart.yaml according to semver.
  • Variables are documented in the README.md
  • Title of the PR starts with chart name (e.g. [<name_of_the_chart>])

@mpgxvii
Copy link
Member

mpgxvii commented Sep 30, 2024

Thanks for this. I was also running into an issue with the healthcheck:

livenessProbe:
httpGet:
path: {{ .Values.basePath }}/health/alive
port: http
readinessProbe:
httpGet:
path: {{ .Values.basePath }}/health/ready

I've added it temporarily to the image but the endpoint is /api/health/alive. Or should we just remove temporarily?

@yatharthranjan
Copy link
Member Author

Ok, thanks; please make an update here, in that case, to add ../api/... Yes, it is okay to remove it temporarily for testing purposes our production.yaml using

| deployment.customLivenessProbe | object | `{}` | Configure a custom livenessProbe. This overwrites the default object |
| deployment.customReadinessProbe | object | `{}` | Configure a custom readinessProbe. This overwrites the default object |

But please issue a fix here for the correct URL.

@keyvaann
Copy link
Collaborator

keyvaann commented Sep 30, 2024

At the moment charts in the external directory is considered to be the mirror of the upstream chart and during updates they'll be removed and redownloaded from the source. If you want to make changes to it, I suggest either moving it to the charts directory or applying the changes in RADAR-Kubernetes repo.

@yatharthranjan
Copy link
Member Author

Yes good point, @mpgxvii i think we can move this to the charts directory as it is maintained by RADAR-base and not externally.

Copy link

github-actions bot commented Oct 4, 2024

Great PR! Please pay attention to the following items before merging:

Files matching charts/*/values.yaml:

  • Is the PR adding a new container? Please reviewer, add it to the models (internal process)
  • Is the PR adding a new parameter? Please, ensure it’s documented in the README.md

This is an automatically generated QA checklist based on modified files.

@mpgxvii mpgxvii requested a review from keyvaann October 4, 2024 15:33
@mpgxvii
Copy link
Member

mpgxvii commented Oct 4, 2024

@keyvaann @yatharthranjan I've made the changes, but I'm not sure why the helm-docs lint check is failing. Is it because I moved it to a new directory?

@keyvaann
Copy link
Collaborator

keyvaann commented Oct 5, 2024

@mpgxvii did you run make gen command?

@mpgxvii
Copy link
Member

mpgxvii commented Oct 6, 2024

@mpgxvii did you run make gen command?

@keyvaann Yeah but it wasn't changing anything. Apparently it was my helm-docs version. Updated this now.

Copy link
Collaborator

@keyvaann keyvaann left a comment

Choose a reason for hiding this comment

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

LGTM

@mpgxvii mpgxvii merged commit 7dff890 into main Oct 6, 2024
5 checks passed
@mpgxvii mpgxvii deleted the fix_sep_ui branch October 6, 2024 15:01
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.

3 participants