-
Notifications
You must be signed in to change notification settings - Fork 315
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
Cluster Peering #1273
Cluster Peering #1273
Commits on Jun 16, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 2c6eb17 - Browse repository at this point
Copy the full SHA 2c6eb17View commit details -
PeeringAcceptor controller (#1225)
Adds new PeeringAcceptor CRD and controller with unit tests. This controller determines whether to generate a new peering token in Consul by reconciling the PeeringAcceptor resource. It currently supports writing the peering token to a K8s secret. Generating the new CRD and API: After updating control-plane/PROJECT L6 to reference the control plane folder, ran the command: `operator-sdk create api --group consul --version v1alpha1 --kind Peering --controller --namespaced=true --make=false --resource=true`
Configuration menu - View commit details
-
Copy full SHA for 5f317b5 - Browse repository at this point
Copy the full SHA 5f317b5View commit details -
PeeringDialer controller (#1236)
PeeringDialer CRD and controller, not including unit tests.
Configuration menu - View commit details
-
Copy full SHA for 4608c90 - Browse repository at this point
Copy the full SHA 4608c90View commit details -
Configuration menu - View commit details
-
Copy full SHA for db6f47e - Browse repository at this point
Copy the full SHA db6f47eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3e848cf - Browse repository at this point
Copy the full SHA 3e848cfView commit details -
Backfill unit tests for peering dialler (#1265)
- Clean up some of the logic in peering dialler and acceptor - Rename handler -> connectWebhook
Configuration menu - View commit details
-
Copy full SHA for 636816e - Browse repository at this point
Copy the full SHA 636816eView commit details -
Add Peer field to Intention CRD source intention (#1263)
update source intentions with peer name and bump api module and change initiate -> establish
Configuration menu - View commit details
-
Copy full SHA for 0b38248 - Browse repository at this point
Copy the full SHA 0b38248View commit details -
Add finalizers to peering acceptor and dialer
- Remove ownerRef from secret created by acceptor.
Configuration menu - View commit details
-
Copy full SHA for d2fa0ad - Browse repository at this point
Copy the full SHA d2fa0adView commit details -
add a helm value for cluster peering
- when global.peering.enabled is true, and connectInject.enabled is true, enable the peering controllers and the peering CRDs.
Configuration menu - View commit details
-
Copy full SHA for e9f53c4 - Browse repository at this point
Copy the full SHA e9f53c4View commit details -
Address review comments to Peering Acceptor and Dialer.
- rename exported service CRD consumer.peerName field from peerName --> peer - rename ConnectWebhook --> MeshWebhook - add some missing unit test cases - only add permissions to connect-inject service account for peering CRs when peering is enabled
Configuration menu - View commit details
-
Copy full SHA for ac0e7b3 - Browse repository at this point
Copy the full SHA ac0e7b3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 430e52f - Browse repository at this point
Copy the full SHA 430e52fView commit details