Upgrade Concourse to version 5.4.1
During the comming days, we’ll roll out Concourse version 5.4.1 to all our setups.
More …Upgrade to EKS 1.13
We have updated our AWS EKS-based reference solution to be compatible with Kubernetes 1.13. More specifically, EKS uses K8s v1.13.10.
More …Concourse task that checks the status of the service after the deployment
We extended the functionallity for the ECS deployments with concourse. After the service gets deployed Concourse would just exit because Terraform doesn’t take the deployment itself into account. This resulted in having false deploys sometimes without any clear reason what happened.
More …Prometheus-blackbox-exporter available as optional cluster addon
We’ve added the prometheus-blackbox-exporter as a K8s cluster addon which can be enabled upon request. The blackbox exporter can be used for probing HTTP(S), DNS, TCP and ICMP endpoints, for example to check whether an external resource is up/down.
More …Redshift monitoring via Prometheus
We have updated our stacks to support Redshift monitoring via the Prometheus Operator running on our K8s clusters. If you have Redshift running, you will now be able to see alerts in Alertmanager and on slack when there is something wrong with the cluster.
Neo4j monitoring via Prometheus
We have updated our stacks to support Neo4j monitoring (Neo4j >= 3.4) via the Prometheus Operator running on our K8s clusters. If you have Neo4j running, you will see metrics appearing in the new Neo4j Grafana dashboard.
Fix for dashboards HTTP 500 error when refreshing token
Since our SSO overhaul you might’ve been noticing sudden HTTP 500 errors while using the Alertmanager, Kubernetes of Prometheus dashboards when your token’s TTL expires.
More …A note on CVE-2019-11247
Two weeks ago a patch for Kubernetes vulnerability CVE-2019-11247 was released for K8s 1.13, 1.14 and 1.15. Unfortunately as of writing clusters using older K8s versions (like our kops-based 1.11 clusters) are still vulnerable.
More …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.
Add Bitbucket, GitLab and Google authentication to Concourse
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 …Kubernetes add-on upgrades
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 …We're moving to EKS
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 …Cluster and Persistent Volume backups with Velero 1.0
Staging Kubernetes clusters are now backed up through Heptio Velero. Production rollout is happening in the following days.
More …SSO / OAuth2 overhaul
We’ve completely updated our cluster’s Single-Sign-On setup, adding new features and fixing some long-standing bugs. What has changed:
More …Support for Cognito in ElasticSearch
in v2.3.8 we added support for Cognito and its options to our terraform-awselasticsearch module.
Adding Prometheus monitoring for Elasticsearch on ECS
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.
Move to the AWS provided Kibana
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 …Update kube2iam to 0.10.7
We’ve updated kube2iam to the latest version (0.10.7) on all clusters.
Upgrade Concourse to version 5
During the comming days, we’ll roll out Concourse version 5.0.1 to all our setups.
More …Increased monitoring alerts visibility
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 …