Skip to content

Releases: dave-inc/charts

common-0.9.0-beta.2

12 Feb 18:28
1b1809a
Compare
Choose a tag to compare

Standard Service Template

common-0.9.0-beta.1

05 Feb 23:28
3e908fe
Compare
Choose a tag to compare

Standard Service Template

job-0.2.1

10 Jan 21:46
3b08371
Compare
Choose a tag to compare
  • Added cloudsqlProxy.socketpathEnvName to allow customization of the environment variable name that provides the path to the cloudsql_proxy socket. Defaults to DB_SOCKETPATH

kyverno-policies-0.1.1-beta.10

09 Jan 00:53
6ca785a
Compare
Choose a tag to compare

A Helm chart for deploying kyverno policies

kyverno-policies-0.1.1-beta.9

08 Jan 20:39
61ae0ff
Compare
Choose a tag to compare
  • Remove whitelist allow reporter to show failures in all namespaces
  • Update label policy search for label in metadata and spec

csm-edgeproxy-0.1.4

08 Jan 20:39
61ae0ff
Compare
Choose a tag to compare

Cloud Service Mesh (Istio) Gateway Edgeproxy

csm-edgeproxy-0.1.3

17 Dec 21:26
3f48f13
Compare
Choose a tag to compare

Cloud Service Mesh (Istio) Gateway Edgeproxy

csm-edgeproxy-0.1.2

17 Dec 20:55
1173b3f
Compare
Choose a tag to compare

Cloud Service Mesh (Istio) Gateway Edgeproxy

common-0.8.10

17 Dec 23:05
99c7a90
Compare
Choose a tag to compare

This version fixes a bug on the common charts to implement the Cloud Armor backend services specifically when it has more than one service resulting that only the main or primary backend service will have annotated its backendConfig and security policy properly but others not and created a security flaw for the remaining services, also know as Backend security policy not applied.

This is a release version of previous 0.8.10-beta.x versions to render CA services based on CA backend service definition, which requires to comply with the following:

  • service name should be named/renamed as "[deployment-name]-ca", ca extension is important because that going fwd will be the identifier of CA services apart from others.
  • We are exposing the targetPort when CA services doesn't share the same across deployments, because its backward compatibility if targetPort is not specified will be defaulted using the CA main deployment port as it's target.
  • It still should comply with the previous requisites but now the backed service name can be used like this:
cloudArmor:
    enabled: true
    paths:
      - backend:
          service:
            name: <your-service-name>-ca
            port:
              number: 80
            targetPort: 8080
  • Fixes CA service render logic to avoid duplicating it whenever the backend service for CA it is the same
  • Fix duplicate lifecycle bug in cloudsqlProxy in common chart

common-0.8.10-beta.4

13 Dec 15:12
29b3b78
Compare
Choose a tag to compare

Fix CA service render logic to avoid duplicating it whenever the backend service for CA it is the same (papi scenario)