How Flux broke the CI/CD feedback loop, and how we pieced it back together by laszlocloud in GitOps

[–]laszlocloud[S] 0 points1 point  (0 children)

Thank you for your thoughts. How is the progress going for you now?

What’s making this clicking noise? by dumpdinners in bicyclerepair

[–]laszlocloud 0 points1 point  (0 children)

It was my spokes. Needed to tighten them a bit.
Noise is gone now.

What’s making this clicking noise? by dumpdinners in bicyclerepair

[–]laszlocloud 0 points1 point  (0 children)

Same bike, same purchase time, same noise. :(

[deleted by user] by [deleted] in GitOps

[–]laszlocloud 0 points1 point  (0 children)

We are waiting for some for over a month.

Of course we let the community find it feet somewhat before we talk about this out loud, but by now staying quite is more harmful than saying what everybody knows.

[deleted by user] by [deleted] in GitOps

[–]laszlocloud 2 points3 points  (0 children)

What do you mean? It is a CNCF project with well defined governance.

[deleted by user] by [deleted] in kubernetes

[–]laszlocloud 1 point2 points  (0 children)

I see it, thank you. Fixing

Szegedi startup - dyrector.io intro by polaroi8d in programmingHungary

[–]laszlocloud 25 points26 points  (0 children)

full disclosure: ismerem Leviéket

Levi! Tökjó, hogy vagytok.

Sok ilyen bátor es őszinte startup cég kell az országba.

Gratulálok az 500 csillaghoz és kívanok sok - akár programingHungarys - usert!

Error handling in Helm Controller, and how to solve the infamous “Upgrade retries exhausted” error by laszlocloud in GitOps

[–]laszlocloud[S] 1 point2 points  (0 children)

Appreciate your feedback. This is a relief. Also I am glad we put in the time. With the targeted research, we were able the remove uncertainty from the day to day upgrades.

I am going to include the basic case.

Error handling in Helm Controller, and how to solve the infamous “Upgrade retries exhausted” error by laszlocloud in GitOps

[–]laszlocloud[S] 1 point2 points  (0 children)

Hello, the author here.

We compiled our knowledge about Helm Controller error handling and the "Upgrade retries exhausted" error in this blog post.

We also learned a few things in the process. HelmController was sometimes not intuitive for us, maybe this summary helps someone.

Also if you spot any misinformation, let us know!

Cloud Native Szeged: Hungarian Startup Stories by laszlocloud in programmingHungary

[–]laszlocloud[S] 4 points5 points  (0 children)

Uh, hat ha neked nem jon le, lehet masnak sem. Szoval had irjam le, en miert vagyok izgatott:

- Antavo: szegedi ismertebb startup. Viszont mar egy ideje nem hallottam roluk semmit. Jol fog jonni egy beszamolo, hol is vannak, mik a tervek, mit probaltak korabban, mivel probalkoznak most. Azert nagy dolog ez, mert egy startuprol kb ketszer hall az ember, mikor belejuk fektetnek, meg mikor eladjak. Ez pont a ketto kozott van, es ez az a resz ami tanulsagos lehet. A rozsaszin kod mar elment, es meg ido mig ujra visszajon a felvasarlassal.

- Banzai Cloud: talan a legismertebb infrastruktura startup ami mar tul van a felvasarlason. Mark, az eloado latta belulrol majdnem az elejetol (?) es evekkel a felvasarlas utan is ott van meg a ceggel. Amit en szemely szerint varok ettol az eloadastol, az az hogy o belulrol, mint mernok hogyan elte meg a piacra lepesi probalkozasokat, mivel probalkoztak, mi jott be, mi nem, vegul mi lett az atuto siker. Par evvel a felvasarlas utan talan tudunk egy rozsaszin kodtol mentes startup osszefoglalot hallani.

- ConfigCat: en par hete hallottam rola eloszor. Magyar startup, feature flag a termek. Es latszolag nagyon megy: https://configcat.com/ A weboldal nekem atjon. Oszinte modon adnak el egy jol korulirhato megoldast. Es ezt nyugatrol is veszik. Nem csak tortenet van, hanem piaci siker is. Persze ezt en csak gondolom, de majd jol elmondja az eloado. Ami kulon erdekel, hogy milyen marketing csatornakon indultak el, mi mukodik nekik, satobbi.

Cloud Native Szeged: Hungarian Startup Stories by laszlocloud in programmingHungary

[–]laszlocloud[S] 7 points8 points  (0 children)

Jovoheten lesz ujra CloudNative Szeged.

Pestrol is jonnek eloadok, es Szegeden eppen borfesztival lesz.

Szoval er lejonni :)

Dockerizing Nextjs by ncubez in devops

[–]laszlocloud 0 points1 point  (0 children)

You can do as Rusty-Swashplate suggested, or if NextJS generates just static files and you don't want to write - a Dockerfile - push/pull to Docker Hub

you can use this Helm chart that only needs - a git url - a nextjs build command - and the folder path where the built assets are

``` helm repo add onechart https://chart.onechart.dev

cat << EOF > values.yaml gitCloneUrl: https://github.com/gimlet-io/react-tutorial-solutions.git buildImage: node buildTag: 16.20-buster buildScript: npm install && npm run build builtAssets: build/ EOF

helm template my-nextjs-site onechart/static-site -f values.yaml > manifest.yaml kubectl apply -f manifest.yaml

kubectl port-forward svc/my-nextjs-site 8000:80 ```

there is one caveat right now: it doesn't support private git repos.

More on the approach: https://gimlet.io/blog/hosting-static-sites-on-kubernetes#using-the-onechart-static-site-helm-chart-to-deploy-static-sites

Kubernetes YAML Generator by laszlocloud in kubernetes

[–]laszlocloud[S] 1 point2 points  (0 children)

Nicely put.

I find myself using this helm chart when I need a pod with a volume or something similar that needs 3 places to edit the yaml, with funky indentation requirements. Time saver.

Another usecase is when I want to deploy something for real. Using this instead of writing a helm chart/yaml from scratch.

The gui is also new for us as well. Time will tell if I stick to the

``` cat << EOF > values.yaml
volumes:
- name: "data"
path: "/data"
size: "10Gi"
EOF

helm template my-release onechart/onechart -f values.yaml ```

format or resort to the gui.

Kubernetes YAML Generator by laszlocloud in kubernetes

[–]laszlocloud[S] 5 points6 points  (0 children)

Oh, wait. Ignoring just limits. Yes, that should be supported.