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

refactoring helm chart #5353

Merged
merged 14 commits into from
Mar 29, 2023
Merged

refactoring helm chart #5353

merged 14 commits into from
Mar 29, 2023

Conversation

nithyatsu
Copy link
Contributor

Description

rad install --set command can now be used to set helm values.
This PR is to refactor helm values.yaml structure and provide final documentation for different values that can be set using rad install set.

Issue reference

Fixes: #5343

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Adds necessary unit tests for change
  • Adds necessary E2E tests for change
  • Unit tests passing
  • Extended the documentation / Created issue for it

@github-actions
Copy link

60.4

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.4 %
  • main branch coverage: 60.4 %
  • diff coverage: 0 %

The coverage result does not include the functional test coverage.

@github-actions
Copy link

60.4

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.4 %
  • main branch coverage: 60.4 %
  • diff coverage: 0 %

The coverage result does not include the functional test coverage.

@github-actions
Copy link

60.4

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.4 %
  • main branch coverage: 60.4 %
  • diff coverage: 0 %

The coverage result does not include the functional test coverage.

@github-actions
Copy link

60.4

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.4 %
  • main branch coverage: 60.4 %
  • diff coverage: 0 %

The coverage result does not include the functional test coverage.

@github-actions
Copy link

60.4

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.4 %
  • main branch coverage: 60.4 %
  • diff coverage: 0 %

The coverage result does not include the functional test coverage.

@github-actions
Copy link

60.4

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.4 %
  • main branch coverage: 60.4 %
  • diff coverage: 0 %

The coverage result does not include the functional test coverage.

@nithyatsu nithyatsu marked this pull request as ready for review March 28, 2023 23:50
@nithyatsu nithyatsu requested a review from a team as a code owner March 28, 2023 23:50
@nithyatsu nithyatsu requested a review from youngbupark March 28, 2023 23:50
@@ -41,9 +41,9 @@ spec:
value: 'true'
- name: SKIP_AUTH
value: 'true'
{{ if .Values.global.rp.publicEndpointOverride}}
{{ if .Values.publicEndpointOverride}}

Choose a reason for hiding this comment

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

I just want to confirm. Since it is a subchart, it does not need to be .Values.rp.publicEndpointOverride, does it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh yes! I have missed it, i will fix it now.

Copy link
Contributor Author

@nithyatsu nithyatsu Mar 29, 2023

Choose a reason for hiding this comment

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

sorry I misread your question. When we do the subcharts, to the subchart, the "subchart:" section in umbrella chart appears just as if it were set in the subchart's local values. file. Therefore we just say Values.publicEndpointOverride. template engine takes care of it..

Comment on lines 323 to 324
aws["accessKeyId"] = awsProvider.AccessKeyId
aws["secretAccessKey"] = awsProvider.SecretAccessKey

Choose a reason for hiding this comment

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

We do not need L323-L324 since there are no code referring to them in helm chart.

"accessKeyId": awsProvider.AccessKeyId,
"secretAccessKey": awsProvider.SecretAccessKey,
"region": awsProvider.TargetRegion,
}

Choose a reason for hiding this comment

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

Can you please remove addAzureProviderValues too ?

Copy link

@youngbupark youngbupark left a comment

Choose a reason for hiding this comment

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

I left minor comments. Please address them before merging :) Also please validate the values in helm chart too.

deploy/Chart/Chart.yaml Outdated Show resolved Hide resolved
deploy/Chart/charts/rp/Chart.yaml Outdated Show resolved Hide resolved
deploy/Chart/values.yaml Show resolved Hide resolved
Copy link
Contributor

@ytimocin ytimocin left a comment

Choose a reason for hiding this comment

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

LGTM other than a few nits

version: '42.42.42-dev'
repository: "file://appcore-rp"
repository: "file://rp"
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this also be radius-rp?

@@ -1,5 +1,5 @@
apiVersion: v2
name: appcore-rp
name: rp
Copy link
Contributor

Choose a reason for hiding this comment

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

radius-rp?

Comment on lines 20 to 24
#
# Configure global.zipkin.url to enable distributed trace
# zipkin:
# url: "http://jaeger-collector.radius-monitoring.svc.cluster.local:9411/api/v2/spans"
#
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this also an example?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes :)

Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Could you add "Example" in the comments?

Copy link
Contributor

@vinayada1 vinayada1 left a comment

Choose a reason for hiding this comment

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

added a nit

@github-actions
Copy link

60.6

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.6 %
  • main branch coverage: 60.5 %
  • diff coverage: .1 %

The coverage result does not include the functional test coverage.

name: appcore-rp
description: Applications.Core Radius service
name: radius-rp
description: Radius service
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
description: Radius service
description: Radius service

# aws:
# region:"us-east"
radius-rp:
image: radius.azurecr.io/appcore-rp
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we plan to change the image to radius-rp as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

not sure.. @youngbupark , should I create a ticket for renaming image?

pkg/cli/helm/radiusclient.go Show resolved Hide resolved
@github-actions
Copy link

60.6

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.6 %
  • main branch coverage: 60.5 %
  • diff coverage: .1 %

The coverage result does not include the functional test coverage.

@github-actions
Copy link

60.6

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

  • Your PR branch coverage: 60.6 %
  • main branch coverage: 60.5 %
  • diff coverage: .1 %

The coverage result does not include the functional test coverage.

@nithyatsu nithyatsu merged commit 7617329 into main Mar 29, 2023
@nithyatsu nithyatsu deleted the helming branch March 29, 2023 19:23
Copy link
Contributor

@kachawla kachawla left a comment

Choose a reason for hiding this comment

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

Should this client be updated as well to expect updated keys? https://github.com/project-radius/radius/blob/main/pkg/cli/helm/radiusclient.go#L245

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.

Simplify helm chart value options.
5 participants