This repository contains the default sets of addons needed to bootstrap D2iQ Kubernetes.
The structure of this repository follows the Kubeaddons Catalog Documentation in reference, and uses the Addon Revision concept covered therein.
You will find the following directories here:
addons/- containing the actual manifests for addon resourcesmetadata/- containing static metadata for the addons inaddons/test/- containing integration tests for the addons inaddons/
There is no community support for this software at this time, and this repository (while publicly visible) is only intended for consumption by D2iQ personnel.
If you are here looking for addon support as an end-user, support is given as per the support provided for your D2iQ Ksphere Solution's provided enterprise support (solutions such as Konvoy), but support is not given directly via this repository.
Please contact D2iQ for questions and more information.
Releases signify a single supported instance of kubernetes-base-addons. They undergo significant integration and soak testing and must be used together to be supported. Any variation from these sets will not be supported.
While you may see other tags in our releases page the only releases which are official and supported releases are named with the prefix stable and not marked as prerelease.
NOTE: Do not use master for production. Instead, pick a supported release version.
For the release process, see the release document.
The master branch of kubernetes-base-addons has made a hard transition to cert-manager v1. Prior to this change, this repository was using the v1alpha1 resource definition which cannot be upgraded to v1alpha2 or beyond.
Releases from this branch will be tagged with the major version 3.
release/2 is going to have backports of changes made to master in order to continue to support cert-manager v1alpha1.
The releases cut from this branch will be major version 2.
The test suite can be exercised locally by running
make test
Pull Requests against this repo is tested by Teamcity and Dispatch.
NOTE: E2E tests for the UI are only run in Dispatch.
Dispatchfile defines the config and exercises the test in the Makefile.
See our Contributing Documentation.