GitLab о своём опыте переезда в Kubernetes
* Используют GKE
* Делали canary при переезде
* Все их конфигурационные файлы лежат в открытом доступе
* После миграции увидели возросший cross-AZ трафик (что стоит денег)
* Как и все, обожглись об resources requests/limits
* По пути улучшили observability и сделали разные другие оптимизации
Вообще, большие миграции хороши тем, что позволяют не только, собственно, смигрировать; но и вычистить по пути кучу мусора, до которого руки всё никак не доходили.
#gitlab #kubernetes
* Используют GKE
* Делали canary при переезде
* Все их конфигурационные файлы лежат в открытом доступе
* После миграции увидели возросший cross-AZ трафик (что стоит денег)
* Как и все, обожглись об resources requests/limits
* По пути улучшили observability и сделали разные другие оптимизации
Вообще, большие миграции хороши тем, что позволяют не только, собственно, смигрировать; но и вычистить по пути кучу мусора, до которого руки всё никак не доходили.
#gitlab #kubernetes
about.gitlab.com
What we learned after a year of GitLab.com on Kubernetes
It's been one year since we moved GitLab.com to Kubernetes. We unpack the challenges and learnings from this major migration.
GitLab issued new security releases: 14.5.2, 14.4.4, and 14.3.6
These releases contain patches for various security vulnerabilities, including one with High severity.
So, if you're running your own GitLab Community Edition (CE) or Enterprise Edition (EE), make sure to upgrade!
#gitlab #security
These releases contain patches for various security vulnerabilities, including one with High severity.
So, if you're running your own GitLab Community Edition (CE) or Enterprise Edition (EE), make sure to upgrade!
#gitlab #security
GitLab
GitLab Security Release: 14.5.2, 14.4.4, and 14.3.6
Learn more about GitLab Security Release: 14.5.2, 14.4.4, and 14.3.6 for GitLab Community Edition (CE) and Enterprise Edition (EE).
GitLab is adopting FluxCD as its GitOps engine.
This is process has just started. So, GitLab's own Kubernetes agents remain the same and, according to this article, likely won't be deprecated till 2025. However, the GitOps functionality is transitioned into the maintenance mode.
Also, this article contains the justification behind Flux. Mainly, it was chosen because it fully relies on Kubernetes API, while Argo provides it's own API and UI, which is harder for GitLab folks to integrate into their own product.
#cicd #gitops #gitlab #kubernetes
This is process has just started. So, GitLab's own Kubernetes agents remain the same and, according to this article, likely won't be deprecated till 2025. However, the GitOps functionality is transitioned into the maintenance mode.
Also, this article contains the justification behind Flux. Mainly, it was chosen because it fully relies on Kubernetes API, while Argo provides it's own API and UI, which is harder for GitLab folks to integrate into their own product.
#cicd #gitops #gitlab #kubernetes
about.gitlab.com
GitOps with GitLab: What you need to know about the Flux CD integration
Inside the decision to integrate Flux CD with the GitLab agent for Kubernetes and what it means to you.
👍14😢4🔥1🤔1
With the whole AI hype going on, it's interesting to see how companies are trying to find an application for AI in their products.
Sometimes it's just pure hype, in my opinion. There are some
"AI-powered" tools that existed just fine without AI. However, I personally see three major areas for AI (LLMs to be precise) in the operational field:
- Taking over some boring tasks like writing some Bash, Makefiles and so on.
- Observability: basically explaining alerts to humans and suggest possible solutions. Perhaps, even apply those suggestions.
- Knowledge management. LLM can answer reoccurring questions instead of a support person. You can even try to teach a model based on your internal documentation and so on.
And here are some practical implementations in some of those areas:
- GitLab’s new security feature uses AI to explain vulnerabilities to developers
- Pulumi AI that writes IaC for you.
P.S. The news about GitLab came from our chat. So, if you have any interesting news to share, do not hesitate to join!
#ai #gitlab #pulumi #iac
Sometimes it's just pure hype, in my opinion. There are some
"AI-powered" tools that existed just fine without AI. However, I personally see three major areas for AI (LLMs to be precise) in the operational field:
- Taking over some boring tasks like writing some Bash, Makefiles and so on.
- Observability: basically explaining alerts to humans and suggest possible solutions. Perhaps, even apply those suggestions.
- Knowledge management. LLM can answer reoccurring questions instead of a support person. You can even try to teach a model based on your internal documentation and so on.
And here are some practical implementations in some of those areas:
- GitLab’s new security feature uses AI to explain vulnerabilities to developers
- Pulumi AI that writes IaC for you.
P.S. The news about GitLab came from our chat. So, if you have any interesting news to share, do not hesitate to join!
#ai #gitlab #pulumi #iac
TechCrunch
GitLab’s new security feature uses AI to explain vulnerabilities to developers
Developer platform GitLab today announced a new AI-driven security feature that uses a large language model to explain potential vulnerabilities to developers, with plans to expand this to automatically resolve these vulnerabilities using AI in the future.
👍9❤1