Kubernetes dashboards ERR_TOO_MANY_REDIRECTS bug
During the past days you might’ve been getting ERR_TOO_MANY_REDIRECTS
and or Bad Request - Login session expired
errors. This bug was introduced during last week’s cluster add-ons upgrade.
During the past days you might’ve been getting ERR_TOO_MANY_REDIRECTS
and or Bad Request - Login session expired
errors. This bug was introduced during last week’s cluster add-ons upgrade.
By default we only allowed authenticating to Concourse through GitHub and local users. It’s now possible to plug into other systems like Bitbucket, GitLab or Google.
More …In the following days we’ll be rolling-out a bunch of upgrades to the deployed add-ons on your clusters. You don’t have to do anything to apply these upgrades, we’ll do that for you. And it won’t cause any downtime to the cluster or your applications. We’ll first start with staging clusters, and production clusters will follow after a couple of days.
More …The past months we’ve beeen heavily re-evaluting and testing AWS EKS as base for our reference solution. Today we can consider our platform GA and moving forward all new clusters will be setup using EKS.
More …Staging Kubernetes clusters are now backed up through Heptio Velero. Production rollout is happening in the following days.
More …We’ve completely updated our cluster’s Single-Sign-On setup, adding new features and fixing some long-standing bugs. What has changed:
More …in v2.3.8 we added support for Cognito and its options to our terraform-awselasticsearch module.
Our ECS monitoring solution now supports monitoring Elasticsearch clusters using Elasticsearch Exporter, Prometheus and AlertManager, so we can get notified via slack (critical/warnings) and via OpsGenie (critical) for any issues with ES. This is similar functionality which was already available for customers running on the Kubernetes platform.
We’re in the process of removing our kibana deployment from all the Staging clusters and replacing it with the AWS provided kibana setup that comes with the AWS ElasticSearch service. Production clusters will follow.
More …We’ve updated kube2iam
to the latest version (0.10.7
) on all clusters.
During the comming days, we’ll roll out Concourse version 5.0.1 to all our setups.
More …During the following days we’re going to rollout some changes in how Kubernetes monitoring notifications are delivered. From now on, all notifications comming from the production k8s monitoring system will be shown in our shared slack channel, that is the channel we share with each of our customers. The current notification channels will still work as until now. Here’s an overview of how notifications will work:
More …We are in the process of upgrading our managed Kubernetes clusters from v1.11.6
to v1.11.9
.
We’ve made the AWS Service Operator available for deployment on our managed Kubernetes clusters.
More …Update (18-03-2019): We found out there were enough default alerts covering all cases of cronjob failures. The following alerts are covering different failure cases accordingly:
More …We are in the process of upgrading our staging Kubernetes clusters components to the latest stable releases. Production clusters will follow in 1 to 2 weeks (to be announced) after we have confirmed there are no issues with our customer’s workloads.
More …We have updated the format of the monitoring Slack notifications. You might have already noticed that the monitoring messages in your Slack channels now contain more useful information and are more structured. We’ve already started rolling out the changes in staging clusters and we’ll start rolling them in production clusters during this week.
More …We have updated the clusters to have support for mongodb monitoring, alerts and dashboards. If you have a mongodb cluster you will see that there is now a mongodb dashboard in Grafana and that we added specific alert rules for mongodb in prometheus.
We’ve upgraded all the k8s cluster with a new etcd backup implementation. The old backup solution was relying on daily snapshots taken from a service running in the master nodes.
More …Update: Added other affected services next to Kubernetes.
More …