We’ve upgraded all the Concourse setups to the latest available version, that’s 4.2.1. As you might have read in the previous post from concourse we were working on the upgrade to Concourse 4.1. During that process we ran into some bugs that we had to mitigate. Early this week Concourse released v4.2 and a day later 4.2.1. We decided to immediately upgrade our test cluster to this version and when everything was stable also upgrade our customer clusters.
More …We’ve upgraded all the Concourse setups to the latest available version, that’s 4.1.0.
We have upgraded our test concourse cluster from v3.14.1 to v4.1.0. Customer clusters will follow shortly after we have confirmed there are no issues with our workloads.
Update: Changed Kubernetes update from 1.10.7 to 1.10.8
More …Some of our infrastructure components were logging extensively to CloudWatch logs and Elasticsearch, filling up precious disk space for our customers. We have now reduced the logging verbosity of those components.
We’ve improved the monitoring for the Kubernetes clusters monitoring component, a.k.a. Calico. We’ll now have more insights in how the networking is behaving in case of trouble. You’ll see there’s an extra dashboard in Grafana showing some interesting metrics from Calico.
The AWS Inspector agent is now installed by default on all nodes. Get in touch if you’d like to configure Inspector Assessments.
We’ve rolled out an OIDC proxy in front of all dashboards of your Kubernetes cluster, including Grafana and Prometheus. So you can access those dashboards via GitHub authentication, instead of needing to go through a VPN.
We’ve upgraded all the Concourse setups to the latest available version, that’s 3.14.1.
More …