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

Add helm value to enable cluster peering #1270

Merged
merged 2 commits into from
Jun 13, 2022
Merged

Conversation

ndhanushkodi
Copy link
Contributor

@ndhanushkodi ndhanushkodi commented Jun 13, 2022

Changes proposed in this PR:

  • when global.peering.enabled is true, and connectInject.enabled is true, enable the peering controllers and the peering CRDs.

How I've tested this PR:
unit tests

How I expect reviewers to test this PR:
👀

Checklist:

  • Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)

Copy link
Contributor

@thisisnotashwin thisisnotashwin left a comment

Choose a reason for hiding this comment

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

This looks great! have a question about marking this feature as TECH PREVIEW in the values file

@@ -29,6 +29,13 @@ global:
# Consul into Kubernetes will have, e.g. `service-name.service.consul`.
domain: consul

# Configures the Cluster Peering feature.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we mark this with [TECH PREVIEW] or something?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i added [Experimental] for this and the CRD fields

Copy link
Contributor Author

Choose a reason for hiding this comment

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

would [Tech Preview] make more sense? I thought it might be a more internal word?

Copy link
Contributor

Choose a reason for hiding this comment

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

yup!! :)

Comment on lines +34 to +37
# If true, the Helm chart will enable Cluster Peering for the cluster. This will enable peering controllers and
# allow use of the PeeringAcceptor and PeeringDialer CRDs to establish peerings for service mesh.
# @type boolean
enabled: false
Copy link
Member

Choose a reason for hiding this comment

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

Should say which version is required

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added this for the peering block, thanks!

Copy link
Contributor

@thisisnotashwin thisisnotashwin left a comment

Choose a reason for hiding this comment

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

EXCELLENT!

@ndhanushkodi ndhanushkodi changed the title add a helm value for cluster peering Add helm value to enable cluster peering Jun 13, 2022
@ndhanushkodi ndhanushkodi merged commit c9fef42 into peering Jun 13, 2022
@ndhanushkodi ndhanushkodi deleted the peering-helm-value branch June 13, 2022 20:49
@ndhanushkodi ndhanushkodi restored the peering-helm-value branch June 13, 2022 21:49
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.

4 participants