release 0.16.0-alpha.0

- publish images and chart to ECR Public
- overdue chart and images rename: multicluster-scheduler -> admiralty
- add note about token expiry in quick start
- upgrade cert-manager in e2e and quick start to 1.13.1

Signed-off-by: adrienjt <adrienjt@users.noreply.github.com>

build/build_one.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright 2021 The Multicluster-Scheduler Authors.
+# Copyright 2023 The Multicluster-Scheduler Authors.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -18,7 +18,7 @@
 set -euo pipefail
 
 # constants
-default_bin_prefix=multicluster-scheduler-
+default_bin_prefix=admiralty-
 
 # environment variables
 # required

charts/multicluster-scheduler/Chart.yaml

@@ -1,18 +1,18 @@
 apiVersion: v2
-name: multicluster-scheduler
-version: 0.15.1
+name: admiralty
+version: 0.16.0-alpha.0
 #kubeVersion: A SemVer range of compatible Kubernetes versions (optional)
 description: A system of Kubernetes controllers that intelligently schedules workloads across clusters.
 type: application
 #keywords:
 #  - A list of keywords about this project (optional)
-home: https://github.com/admiraltyio/multicluster-scheduler
+home: https://github.com/admiraltyio/admiralty
 #sources:
-#  - https://github.com/admiraltyio/multicluster-scheduler
+#  - https://github.com/admiraltyio/admiralty
 #maintainers: # (optional)
 #  - name: The maintainer's name (required for each maintainer)
 #    email: The maintainer's email (optional for each maintainer)
 #    url: A URL for the maintainer (optional for each maintainer)
 icon: https://admiralty.io/icons/icon-144x144.png
-appVersion: 0.15.1
+appVersion: 0.16.0-alpha.0
 #deprecated: Whether this chart is deprecated (optional, boolean)

charts/multicluster-scheduler/README.md

@@ -1,14 +1,14 @@
-# Multicluster-Scheduler Helm Chart
+# Admiralty Helm Chart
 
-Multicluster-Scheduler is a system of Kubernetes controllers that intelligently schedules workloads across clusters. This document details the parameters of the chart, and discusses our use of a Helm post-delete hook. For general information about the project and installation instructions, see the [main README](../../README.md).
+Admiralty is a system of Kubernetes controllers that intelligently schedules workloads across clusters. This document details the parameters of the chart, and discusses our use of a Helm post-delete hook. For general information about the project and installation instructions, see the [main README](../../README.md).
 
 > Note: This chart was built for Helm v3.
 
-> Note: multicluster-scheduler doesn't support clusters without RBAC. There's no `rbac.create` parameter.
+> Note: Admiralty doesn't support clusters without RBAC. There's no `rbac.create` parameter.
 
 ## Post-Delete Hook
 
-Multicluster-scheduler uses [finalizers](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#finalizers) for [cross-cluster garbage collection](https://twitter.com/adrienjt/status/1199467878015066112). In particular, it adds finalizers to proxy pods, global services, and config maps and secrets mounted by multi-cluster pods. The finalizers block the deletion of those objects until multicluster-scheduler deletes their delegates in other clusters. If multicluster-scheduler stopped running, and those finalizers weren't removed, object deletions would be blocked indefinitely. Therefore, when multicluster-scheduler is uninstalled, a Kubernetes job will run as a [Helm post-delete hook](https://helm.sh/docs/topics/charts_hooks/) to clean up the finalizers.
+Admiralty uses [finalizers](https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#finalizers) for [cross-cluster garbage collection](https://twitter.com/adrienjt/status/1199467878015066112). In particular, it adds finalizers to proxy pods, global services, and config maps and secrets mounted by multi-cluster pods. The finalizers block the deletion of those objects until Admiralty deletes their delegates in other clusters. If Admiralty stopped running, and those finalizers weren't removed, object deletions would be blocked indefinitely. Therefore, when Admiralty is uninstalled, a Kubernetes job will run as a [Helm post-delete hook](https://helm.sh/docs/topics/charts_hooks/) to clean up the finalizers.
 
 ## Parameters
 
@@ -19,34 +19,34 @@ Multicluster-scheduler uses [finalizers](https://kubernetes.io/docs/tasks/access
 | fullnameOverride | string | `""` | Override chart and release names in object names |
 | imagePullSecretName | string | `""` |  |
 | controllerManager.replicas | integer | `2` |  |
-| controllerManager.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-agent"` |  |
-| controllerManager.image.tag | string | `"0.15.1"` |  |
+| controllerManager.image.repository | string | `"public.ecr.aws/v7x5q9o1/admiralty-agent"` |  |
+| controllerManager.image.tag | string | `"0.16.0-alpha.0"` |  |
 | controllerManager.image.pullPolicy | string | `"IfNotPresent"` |  |
 | controllerManager.resources | object | `{}` |  |
 | controllerManager.nodeSelector | object | `{}` |  |
 | controllerManager.securityContext | object | `{}` |  |
 | controllerManager.affinity | object | `{}` |  |
 | controllerManager.tolerations | array | `[]` |  |
 | scheduler.replicas | integer | `2` |  |
-| scheduler.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-scheduler"` |  |
-| scheduler.image.tag | string | `"0.15.1"` |  |
+| scheduler.image.repository | string | `"public.ecr.aws/v7x5q9o1/admiralty-scheduler"` |  |
+| scheduler.image.tag | string | `"0.16.0-alpha.0"` |  |
 | scheduler.image.pullPolicy | string | `"IfNotPresent"` |  |
 | scheduler.resources | object | `{}` |  |
 | scheduler.nodeSelector | object | `{}` |  |
 | scheduler.securityContext | object | `{}` |  |
 | scheduler.affinity | object | `{}` |  |
 | scheduler.tolerations | array | `[]` |  |
-| postDeleteJob.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-remove-finalizers"` |  |
-| postDeleteJob.image.tag | string | `"0.15.1"` |  |
+| postDeleteJob.image.repository | string | `"public.ecr.aws/v7x5q9o1/admiralty-remove-finalizers"` |  |
+| postDeleteJob.image.tag | string | `"0.16.0-alpha.0"` |  |
 | postDeleteJob.image.pullPolicy | string | `"IfNotPresent"` |  |
 | postDeleteJob.resources | object | `{}` |  |
 | postDeleteJob.nodeSelector | object | `{}` |  |
 | postDeleteJob.securityContext | object | `{}` |  |
 | postDeleteJob.affinity | object | `{}` |  |
 | postDeleteJob.tolerations | array | `[]` |  |
 | restarter.replicas | integer | `2` |  |
-| restarter.image.repository | string | `"quay.io/admiralty/multicluster-scheduler-remove-finalizers"` |  |
-| restarter.image.tag | string | `"0.15.1"` |  |
+| restarter.image.repository | string | `"public.ecr.aws/v7x5q9o1/admiralty-remove-finalizers"` |  |
+| restarter.image.tag | string | `"0.16.0-alpha.0"` |  |
 | restarter.image.pullPolicy | string | `"IfNotPresent"` |  |
 | restarter.resources | object | `{}` |  |
 | restarter.nodeSelector | object | `{}` |  |

charts/multicluster-scheduler/values.yaml

@@ -11,7 +11,7 @@ sourceController:
 controllerManager:
   replicas: 2
   image:
-    repository: "quay.io/admiralty/multicluster-scheduler-agent"
+    repository: "public.ecr.aws/v7x5q9o1/admiralty-agent"
     tag: "" # (default: .Chart.AppVersion)
     pullPolicy: IfNotPresent
   resources: {}
@@ -38,7 +38,7 @@ controllerManager:
 scheduler:
   replicas: 2
   image:
-    repository: "quay.io/admiralty/multicluster-scheduler-scheduler"
+    repository: "public.ecr.aws/v7x5q9o1/admiralty-scheduler"
     tag: "" # (default: .Chart.AppVersion)
     pullPolicy: IfNotPresent
   resources: {}
@@ -64,7 +64,7 @@ scheduler:
 
 postDeleteJob:
   image:
-    repository: "quay.io/admiralty/multicluster-scheduler-remove-finalizers"
+    repository: "public.ecr.aws/v7x5q9o1/admiralty-remove-finalizers"
     tag: "" # (default: .Chart.AppVersion)
     pullPolicy: IfNotPresent
   nodeSelector: {}
@@ -91,7 +91,7 @@ postDeleteJob:
 restarter:
   replicas: 2
   image:
-    repository: "quay.io/admiralty/multicluster-scheduler-restarter"
+    repository: "public.ecr.aws/v7x5q9o1/admiralty-restarter"
     tag: "" # (default: .Chart.AppVersion)
     pullPolicy: IfNotPresent
   nodeSelector: {}

docs/operator_guide/installation.md

@@ -5,12 +5,7 @@ custom_edit_url: https://github.com/admiraltyio/admiralty/edit/master/docs/opera
 
 
 
-1.  [Install Helm v3](https://helm.sh/docs/intro/install/) on your machine if not already installed, as it is the only supported way to install the Admiralty agent at the moment. Once installed, add the Admiralty chart repository:
-
-    ```shell script
-    helm repo add admiralty https://charts.admiralty.io
-    helm repo update
-    ```
+1.  [Install Helm v3](https://helm.sh/docs/intro/install/) on your machine if not already installed, as it is the only supported way to install the Admiralty agent at the moment.
 
     The Admiralty agent must be installed in all clusters that you want to connect. Repeat the following steps for each cluster:
 
@@ -26,8 +21,8 @@ custom_edit_url: https://github.com/admiraltyio/admiralty/edit/master/docs/opera
 1.  Install the Admiralty agent with Helm v3:
 
     ```shell script
-    helm install admiralty admiralty/multicluster-scheduler \
+    helm install admiralty oci://public.ecr.aws/v7x5q9o1/admiralty \
         --namespace admiralty --create-namespace \
-        --version 0.15.1 \
+        --version 0.16.0-alpha.0 \
         --wait
     ```

docs/operator_guide/scheduling.md

@@ -113,7 +113,7 @@ metadata:
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: ClusterRole
-  name: multicluster-scheduler-source
+  name: admiralty-source
 subjects:
   - kind: ServiceAccount
     name: c1
@@ -126,7 +126,7 @@ metadata:
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: ClusterRole
-  name: multicluster-scheduler-cluster-summary-viewer
+  name: admiralty-cluster-summary-viewer
 subjects:
   - kind: ServiceAccount
     name: c1