The Heat Operator deploys the OpenStack Heat project in a Kubernetes cluster.
This project should be used to deploy the OpenStack Heat project. It expects that there is an existing Database and Keystone service available to connect to. The config can be tuned using the defaultConfigOverwrite interface to override default config option in the heat.conf file.
You’ll need a Kubernetes cluster to run against. You can use KIND to get a local cluster for testing, or run against a remote cluster.
Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info shows).
// TODO(bshephar) - Write steps for testing on kind or CRC. Using kind will require that we don't use OpenShift specific CR's like Route.
// TODO(bshephar)
// TODO(bshephar)
// TODO(bshephar): Add detailed information on how you would like others to contribute to this project
This project aims to follow the Kubernetes Operator pattern
It uses Controllers which provides a reconcile function responsible for synchronizing resources untile the desired state is reached on the cluster
// TODO(bshephar)
If you are editing the API definitions, generate the manifests such as CRs or CRDs using:
make manifestsNOTE: Run make --help for more information on all potential make targets
More information can be found via the Kubebuilder Documentation
Copyright 2022.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.