Blog

okctl upgrade does not attempt to upgrade the EKS cluster, because there can be manual, cluster specific changes that need to be done before upgrading. To upgrade, you need to follow this guide: https://github.com/oslokommune/okctl-upgrade/tree/main/gists/bump-eks We will be happy to help if you

Turns out it doesn't make much sense that applications own their namespaces. Turns out namespaces often are shared by multiple applications. Turns out deleting all resources belonging to an app is a problem when one of the resources is shared with other apps. To improve the solution, we've moved the

Persistence in production logs is expected, but it's also a feature. A feature we've postponed long enough. Okctl 0.0.94 configures Loki to use S3 as storage for logs and DynamoDB for index tables. To upgrade, download the latest okctl and run‌‌: okctl upgrade What does it mean for

On March 15, 2022 ArgoCD made with Okctl versions before v0.0.92 will stop working. By "stop working" we mean that ArgoCD will stop deploying your applications. More specifically, it will stop listening for changes in your Okctl IAC git repository. The ArgoCD website will still be running. To

Motivation To save ourselves from having to add --namespace for all kubectl commands we use, we've added a tool called Kubens [https://github.com/ahmetb/kubectx] to okctl venv. What it means for you By running kubens inside okctl venv, Kubens will ensure that all kubectl commands is executed inside

Motivation To remove a manual step in the apply application process and to better adhere to the concept of GitOps, we've now implemented automatic synchronization of ArgoCD application manifest files. What it means for you * You no longer have to run kubectl apply -f after running apply application. * An application's

Okctl 0.0.87 bumps ArgoCD from 1.7.2 to 2.1.7. Any applications that ArgoCD manages will not be removed, so it is safe to run. Q: The upgrade fails, what do I do? In case the upgade fails, you can recover by deleting the existing ArgoCD

We have now released an upgrade for Grafana, which bumps the version from 7.3.5 to 7.5.12. Important! During this upgrade, Grafana will restart. Because we currently have not implemented persistent storage for Grafana, all user settings, including dashboards, will be lost. Technically speaking, the current Kubernetes

This is an article in two parts, written by Paul Beskow and published on Medium in Oct 2020. Part one - Transforming the productization of software — we the people [https://medium.com/@paulbes/transforming-the-productization-of-software-we-the-people-c47a3675f4b6] How including developers in an iterative development process can improve the technical solution. Part two -