kubernetes-charts.suse.com

Pipeline to upload the helm-charts via s3 to https://kubernetes-charts.suse.com

Pipeline to create the container for splatform/concourse-aws-helm

Pipeline to check pull requests against this repo

kubernetes-charts-suse-com's People

Contributors

Stargazers

Watchers

kubernetes-charts-suse-com's Issues

Error on deployments of cf-usb-sidecar-mysql and cf-usb-sidecar-postgres

After deployments of cf-usb-sidecar-mysql and cf-usb-sidecar-postgres, I have Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1". https://kubernetes.io/blog/2019/09/18/kubernetes-1-16-release-announcement/ mentioned the expected error since CaaSP uses 1.18.2 currently.

In order to support CaaSP K8s version, the following needs to be added in the charts.

{{- if semverCompare ">=1.16" (printf "%s.%s" .Capabilities.KubeVersion.Major (trimSuffix "+" .Capabilities.KubeVersion.Minor) )}}
apiVersion: apps/v1
{{- else }}
apiVersion: extensions/v1beta1
{{- end }}
kind: Deployment

CI broken

Seems like the current CI is broken, but But I can't open the CI log successfully.
Please help fix the CI issue 🙇

Start gating PRs with the linting from CI

Currently, PRs can be merged even if their helm linting fails. This makes linting the other helm charts less useful, as everything will be red from then onwards, and responsibility on code health dilutes.

I propose to gate the PRs with the linting pipeline https://github.com/SUSE/cloudfoundry/tree/master/ci/pipelines/helm-charts-check, only being able to merge with explicit approval.

This protects us from #158

Recommend Projects