chore: release main

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.39.0-rc.2"
+  ".": "0.39.0-rc.3"
 }

README.md

@@ -70,7 +70,7 @@ Mac / Linux
 <!-- x-release-please-start-version -->
 
 ```console
-curl --silent --location "https://github.com/weaveworks/weave-gitops/releases/download/v0.39.0-rc.2/gitops-$(uname)-$(uname -m).tar.gz" | tar xz -C /tmp
+curl --silent --location "https://github.com/weaveworks/weave-gitops/releases/download/v0.39.0-rc.3/gitops-$(uname)-$(uname -m).tar.gz" | tar xz -C /tmp
 sudo mv /tmp/gitops /usr/local/bin
 gitops version
 ```

charts/gitops-server/Chart.yaml

@@ -1,21 +1,6 @@
 apiVersion: v2
 name: weave-gitops
 description: Weave Gitops is a set of tools and services to aid your interactions with Flux
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
 type: application
-# This is the chart version. This version number should be incremented each time you make changes
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.39.0-rc.2 # x-release-please-version
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
-appVersion: "v0.39.0-rc.2" # x-release-please-version
+version: 0.39.0-rc.3
+appVersion: 0.39.0-rc.3

charts/gitops-server/values.yaml

@@ -1,108 +1,48 @@
-# Default values for chart.
-# This is a YAML-formatted file.
-# Declare variables to be passed into your templates.
-
-# Note: paragraphs starting with `# --` will end up in our manual -
-# see https://github.com/norwoodj/helm-docs
 replicaCount: 1
 image:
-  # FIXME check the app name
   repository: ghcr.io/weaveworks/wego-app
   pullPolicy: IfNotPresent
-  # Overrides the image tag whose default is the chart appVersion.
-  tag: "v0.39.0-rc.2" # x-release-please-version
+  tag: 0.39.0-rc.3
 imagePullSecrets: []
-nameOverride: ""
-fullnameOverride: ""
-# -- What log level to output. Valid levels are 'debug', 'info', 'warn' and 'error'
+nameOverride: ''
+fullnameOverride: ''
 logLevel: info
-# -- Additional arguments to pass in to the gitops-server
 additionalArgs: []
-# Any other environment variables:
 envVars:
   - name: WEAVE_GITOPS_FEATURE_TENANCY
-    value: "true"
+    value: 'true'
   - name: WEAVE_GITOPS_FEATURE_CLUSTER
-    value: "false"
-  # -- Enable this feature flag if you want to expand Flux Runtime UI with other Weave GitOps components like Policy Agent or TF-Controller.
-  # Ensure that Weave GitOps Deployment and CRDs have the label 'app.kubernetes.io/part-of=weave-gitops'. See https://docs.gitops.weaveworks.org/docs/open-source/getting-started/install-OSS for more info.
+    value: 'false'
   - name: WEAVE_GITOPS_FEATURE_GITOPS_RUNTIME
-    value: "false"
-
-# -- Annotations to add to the deployment
+    value: 'false'
 annotations: {}
-# Should the 'oidc-auth' secret be created. For a detailed
-# explanation of these attributes please see our documentation:
-# https://docs.gitops.weaveworks.org/docs/configuration/securing-access-to-the-dashboard/#login-via-an-oidc-provider
 oidcSecret:
   create: false
-  # clientID:
-  # clientSecret:
-  # issuerURL:
-  # redirectURL:
-  # -- If non empty, additional keys can be added to the OIDC secret
   additionalKeys: {}
-  # additionalKeys:
-  #   claimUsername: "email"
-  #   claimGroups: "groups"
-  #   customScopes: "openid,offline_access,email,groups"
 serviceAccount:
-  # -- Specifies whether a service account should be created
   create: true
-  # -- Annotations to add to the service account
   annotations: {}
-  # -- The name of the service account to use.
-  # If not set and create is true, a name is generated using the fullname template
-  name: ""
+  name: ''
 rbac:
-  # -- Specifies whether the clusterRole & binding to the service account should be created
   create: true
-  # -- If non-empty, this limits the resources that the service
-  # account can impersonate. This applies to both users and groups, e.g.
-  # `['[email protected]', '[email protected]', 'operations']`
   impersonationResourceNames: []
-  # -- Limit the type of principal that can be impersonated
-  impersonationResources: ["users", "groups"]
-  # -- Specifies whether the service account should have cluster-wide view access to secrets.
-  # If enabled, the secrets permitted to read can be limited by name with `viewSecretsResourceNames`.
+  impersonationResources:
+    - users
+    - groups
   viewSecretsEnabled: true
-  # -- If non-empty, this limits the secrets that can be accessed by
-  # the service account to the specified ones, e.g. `['weave-gitops-enterprise-credentials']`
-  viewSecretsResourceNames: ["cluster-user-auth", "oidc-auth"]
-  # -- If non-empty, these additional rules will be appended to the RBAC role and the cluster role.
-  # for example,
-  # additionalRules:
-  # - apiGroups: ["infra.contrib.fluxcd.io"]
-  #   resources: ["terraforms"]
-  #   verbs: [ "get", "list", "patch" ]
+  viewSecretsResourceNames:
+    - cluster-user-auth
+    - oidc-auth
   additionalRules: []
 adminUser:
-  # -- Whether the local admin user should be created.
-  # If you use this make sure you add it to `rbac.impersonationResourceNames`.
   create: false
-  # -- Specifies whether the clusterRole & binding to the admin user should be created.
-  # Will be created only if `adminUser.create` is enabled. Without this,
-  # the adminUser will only be able to see resources in the target namespace.
   createClusterRole: true
-  # -- Whether we should create the secret for the local
-  # adminUser. Will be created only if `adminUser.create` is
-  # enabled. Without this, we'll still set up the roles and
-  # permissions, but the secret with username and password has to be
-  # provided separately.
   createSecret: true
-  # -- Set username for local admin user, this should match the value in the secret `cluster-user-auth`
-  # which can be created with `adminUser.createSecret`. Requires `adminUser.create`.
   username: gitops-test-user
-  # -- (string) Set the password for local admin user. Requires `adminUser.create` and `adminUser.createSecret`
-  # This needs to have been hashed using bcrypt.
-  # You can do this via our CLI with `gitops get bcrypt-hash`.
-  passwordHash:
+  passwordHash: null
 podAnnotations: {}
 podLabels: {}
-# aadpodidbinding: identity
 podSecurityContext: {}
-# fsGroup: 2000
-
 securityContext:
   runAsNonRoot: true
   allowPrivilegeEscalation: false
@@ -117,94 +57,29 @@ service:
   create: true
   type: ClusterIP
   port: 9001
-  # nodePort:
   annotations: {}
 ingress:
   enabled: false
-  className: ""
+  className: ''
   annotations: {}
-  # kubernetes.io/ingress.class: nginx
-  # kubernetes.io/tls-acme: "true"
-  hosts:
-  # - host: chart-example.local
-  #   paths:
-  #     - path: /
-  #       pathType: ImplementationSpecific
-  #
+  hosts: null
   tls: []
-  #  - secretName: chart-example-tls
-  #    hosts:
-  #      - chart-example.local
 extraVolumes: []
 extraVolumeMounts: []
-# Example using extraVolumes and extraVolumeMounts to load 'oidc-auth' secret 
-# with a secrets store CSI driver. Specify the secretName 'oidc-auth' in the 
-# secretProviderClass so this will be created by the secrets store CSI driver.
-# See https://secrets-store-csi-driver.sigs.k8s.io/topics/sync-as-kubernetes-secret.html
-# extraVolumeMounts:
-#   - name: ww-gitops-oauth-volume
-#     mountPath: /mnt/secrets
-#     readOnly: true
-# extraVolumes:
-#   - name: ww-gitops-oauth-volume
-#     csi:
-#       driver: secrets-store.csi.k8s.io
-#       readOnly: true
-#       volumeAttributes:
-#         secretProviderClass: ww-gitops-oauth-provider
 resources: {}
-# We usually recommend not to specify default resources and to leave this as a conscious
-# choice for the user. This also increases chances charts run on environments with little
-# resources, such as Minikube. If you do want to specify resources, uncomment the following
-# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-# limits:
-#   cpu: 100m
-#   memory: 128Mi
-# requests:
-#   cpu: 100m
-#   memory: 128Mi
-
 networkPolicy:
-  # -- Specifies whether default network policies should be created.
   create: true
 nodeSelector: {}
 tolerations: []
 affinity: {}
 serverTLS:
-  # -- Enable TLS termination in gitops itself. If you enable this,
-  # you need to create a secret, and specify the secretName. Another
-  # option is to create an ingress.
   enable: false
-  # -- Specify the tls secret name. This type of secrets have a key called `tls.crt` and `tls.key` containing their corresponding values in  base64 format.
-  # See
-  # https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets for more details and examples
-  secretName: "my-secret-tls"
-  # Example of tls secret
-  #
-  #  apiVersion: v1
-  #  kind: Secret
-  #  metadata:
-  #    name: my-secret-tls
-  #  type: kubernetes.io/tls
-  #  data:
-  #    # the data is abbreviated in this example
-  #    tls.crt: |
-  #      MIIC2DCCAcCgAwIBAgIBATANBgkqh ...
-  #    tls.key: |
-  #      MIIEpgIBAAKCAQEA7yn3bRHQ5FHMQ ...
-  #
-  # You can also create a tls secre t from files whith this k8s command:
-  # kubectl create secret tls my-tls-secret \
-  #  --cert=path/to/cert/file \
-  #  --key=path/to/key/file
+  secretName: my-secret-tls
 metrics:
-  # -- Start the metrics exporter
   enabled: false
   service:
-    # -- Port to start the metrics exporter on
     port: 2112
-    # -- Annotations to set on the service
     annotations:
-      prometheus.io/scrape: "true"
-      prometheus.io/path: "/metrics"
-      prometheus.io/port: "{{ .Values.metrics.service.port }}"
+      prometheus.io/scrape: 'true'
+      prometheus.io/path: /metrics
+      prometheus.io/port: '{{ .Values.metrics.service.port }}'

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@weaveworks/weave-gitops",
-  "version": "0.39.0-rc.2",
+  "version": "0.39.0-rc.3",
   "description": "Weave GitOps core",
   "targets": {
     "default": {