cluster-registry-controller
cluster-registry-controller copied to clipboard
cisco-open
initial e2e CI job with 2 KinD clusters
| Q | A |
|---|---|
| Bug fix? | no |
| New feature? | no |
| API breaks? | no |
| Deprecations? | no |
| Related tickets | none |
| License | Apache 2.0 |
What's in this PR?
Validates the README example via a GH actions job called `e2e`.The job steps:
- build the cluster-registry-controller container
- create 2 KinD clusters
- do the README example steps to validate cluster-registry sync behavior a) install cluster-registry-controller in both clusters via helm chart b) copy cluster CR from c1 to c2 and vice versa c) copy kubeconfig secret from c1 to c2 and vice versa d) check CR status is synced
- publish both clusters'
clusterCR data as job artifacts - cleanup
Why?
This is a representative test workflow to show the capability and config of github actions. There are similar tests in other open source projects, e.g. see NSM interdomain tests. There are no functional tests which validate the behavior of the cluster-registry-controller at the moment.
Additional context
The changes also include an example codespaces setup with a custom devcontainer that is built with all dependencies for KinD testing within the codespace.
Checklist
- [x] Implementation tested
- [ ] User guide and development docs updated (if needed)
