Skip to content

Releases: AMRC-FactoryPlus/amrc-connectivity-stack

v5.0.4

26 Mar 11:48
395dcfa

Choose a tag to compare

What's Changed

Full Changelog: v5.0.3...v5.0.4

v5.0.4-rc.1: Move composite grants into service-accounts (#615)

26 Mar 10:37
2dea0da

Choose a tag to compare

  • Fix CmdEsc permissions, broken in 4.5.0.
  • Trim Directory historical record, it's getting out of hand.

v5.0.3

25 Mar 09:55
e71e1e3

Choose a tag to compare

What's Changed

Full Changelog: v5.0.2...v5.0.3

v5.0.2

10 Mar 17:23
5c2cea0

Choose a tag to compare

What's Changed

Full Changelog: v5.0.1...v5.0.2

v5.0.1

10 Mar 15:02
a33170b

Choose a tag to compare

What's Changed

Full Changelog: v5.0.0...v5.0.1

v5.0.0

09 Mar 14:05
d5f2434

Choose a tag to compare

Upgrade notes

This is a major release of ACS and requires manual intervention on upgrade. Specifically the Flux version upgrade requires manual action on all deployed edge clusters.

Edge clusters with external Flux

These are clusters with bare: true in their Edge cluster configuration config entry. Normally this will only be the case where an edge cluster has been deployed on the same k8s cluster as the ACS central cluster, and that k8s cluster is already managed by Flux.

For these clusters, ensure Flux has been upgraded to at least 2.5.1 before upgrading ACS. If Flux on the edge cluster is upgraded to 2.7.0 or later then the edge cluster deployment will fail to reconcile; this will recover without intervention once ACS is upgraded to 5.0.0.

Edge clusters with Flux deployed by ACS

This is the normal case, where the edge cluster is entirely managed by ACS. For these clusters you will need an environment where you have available

  • Kubernetes API access to each edge cluster, including an appropriate kubeconfig.
  • An appropriate kubectl binary.
  • The Flux binary for version 2.5.1, from here, as flux-2.5.1.
  • The Flux binary for version 2.7.5, from here, as flux-2.7.5.

Upgrade ACS to 5.0.0 on the central cluster first. This will cause the Flux resources on the edge cluster to fail to reconcile, as they will be trying to deploy CR versions that don't exist yet. Now, for each edge cluster, follow these steps:

  • Ensure the environment is set up to contact the correct edge cluster, including the KUBECONFIG environment variable.
  • Run flux-2.5.1 install --export | kubectl apply -f -. This manually installs Flux 2.5.1 on the cluster. This intermediate step is necessary as previously ACS deployed Flux 2.0.0 which has no CRD versions in common with Flux 2.7.5.
  • Wait for the new CRD versions to become available. kubectl get helmreleases.v2.helm.toolkit.fluxcd.io should print 'no resources found' rather than 'server doesn't have resource type'.
  • At this point the fplus-edge/self-link Kustomization should reconcile correctly. If necessary run flux-2.5.1 reconcile ks -n fplus-edge self-link to ensure that it has.
  • Run flux-2.7.5 migrate. This will upgrade all Flux CRs to the latest available storage version. This is necessary before Flux 2.7.5 can be installed as it removes old CRD versions.
  • At this point the fplus-edge/flux-system Kustomization should reconcile correctly. If necessary run flux-2.7.5 reconcile ks -n fplus-edge flux-system to ensure that it has.
  • Verify all running Flux deployments are labelled as Flus 2.7.5. Verify all Flux resources are reconciling correctly.

What's Changed

Full Changelog: v4.5.0...v5.0.0

v4.5.0

03 Mar 15:57
79a3308

Choose a tag to compare

What's Changed

Full Changelog: v4.4.0...v4.5.0

v4.5.0-rc.6

03 Mar 15:33
79a3308

Choose a tag to compare

v4.5.0-rc.6 Pre-release
Pre-release
  • Check that edge helm releases have UUIDs in the name
  • Check OPC UA server

v4.5.0-rc.5

03 Mar 15:22
79a3308

Choose a tag to compare

v4.5.0-rc.5 Pre-release
Pre-release
  • Check that edge helm releases have UUIDs in the name
  • Check OPC UA server

v4.5.0-rc.4

03 Mar 15:16
79a3308

Choose a tag to compare

v4.5.0-rc.4 Pre-release
Pre-release
  • Check that edge helm releases have UUIDs in the name
  • Check OPC UA server