oramawera.blogg.se

With the result and the commit hash it reconciled. After this is done the kustomize-controller sends an event to the notification-controller When a new commit is pushed to the repository, source-controller will sync the commit, triggering the kustomize-controller This can all beĭone without requiring any access to the Kubernetes cluster.Īs stated before the provider works by referencing the same git repository as the Kustomization controller does. That can automatically promote, commit to a new directory, after receiving a successful commit status. This means that a deployment will work in a similar manner that people are used to with “traditional” push based CD pipelines.Īdditionally the status can be fetched from the git providers API for a specific commit. That it closes the deployment loop giving quick and visible feedback if a commit has reconciled and if it succeeded. Receiving an event in the form of a commit status rather than a message in a chat conversation has the benefit

In GitHub the commit status set by notification-controller will result in a green checkmark or red cross next to the commit hash.Ĭlicking the icon will show more detailed information about the status. The linking is done by updating the commit status of a specific commit. Instead ofĪ stateless stream of events, the git notification providers will link the event with accompanying git commit which The GitHub, GitLab, Bitbucket, and Azure DevOps providers are slightly different to the other providers. a Kubernetes object was created, updated or deleted.When the verbosity is set to info, the controller will alert if: This includes kustomize build and validation errors,

When the severity is set to error, the kustomize controller will alert on any errorĮncountered during the reconciliation process. The event severity can be set to info or error. Multiple alerts can be used to send notifications to different channels or Slack organizations.