You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
At the moment, katapult relies on kubectl apply, applying whatever yaml came out of templates.
If something, eg a service, is removed or renamed in templates, kubectl will not remove it or it will create a new renamed service. This happens because kubectl has no notion of the cluster state. Tools like terraform instead do know about that state, and store it in a dedicated file.
Katapult should adopt the approach taken by tools like terraform and deal with the current state of the cluster, so that removing something, eg a service, which it previously created, results in the removal of that service
The text was updated successfully, but these errors were encountered:
At the moment, katapult relies on
kubectl apply
, applying whatever yaml came out of templates.If something, eg a service, is removed or renamed in templates,
kubectl
will not remove it or it will create a new renamed service. This happens becausekubectl
has no notion of the cluster state. Tools liketerraform
instead do know about that state, and store it in a dedicated file.Katapult should adopt the approach taken by tools like terraform and deal with the current state of the cluster, so that removing something, eg a service, which it previously created, results in the removal of that service
The text was updated successfully, but these errors were encountered: