[PTFE-658] Changing registry to ghcr (#46)

Author: gaspardmoindrot

charts/gh-action-exporter/values.yaml

@@ -5,16 +5,15 @@
 replicaCount: 1
 
 image:
-  repository: "registry.scality.com/gh-actions-exporter/gh-actions-exporter"
+  repository: ghcr.io/scality/gh-actions-exporter
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "0.0.1-gamma"
+  tag: 0.0.1-gamma
 
 imagePullSecrets: []
 nameOverride: ""
 fullnameOverride: ""
 
-
 config:
   job_relabelling: []
 
@@ -29,10 +28,12 @@ serviceAccount:
 
 podAnnotations: {}
 
-podSecurityContext: {}
+podSecurityContext:
+  {}
   # fsGroup: 2000
 
-securityContext: {}
+securityContext:
+  {}
   # capabilities:
   #   drop:
   #   - ALL
@@ -46,7 +47,8 @@ service:
 
 ingress:
   enabled: true
-  annotations: {}
+  annotations:
+    {}
     # kubernetes.io/ingress.class: nginx
     # kubernetes.io/tls-acme: "true"
   hosts:
@@ -61,7 +63,8 @@ ingress:
   #    hosts:
   #      - chart-example.local
 
-resources: {}
+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