olafmol

Hi @atombender,

with the new SDK you would be able to parse your K8s manifests, and create (dynamic) configs with the parsed info. This is actually an interesting usecase, tnx!

Could you explain what you mean with "running a single job across multiple machines"? How would that exactly work clustering- and result-agreggation wise? Of course it's perfectly possible to run parallel jobs over multiple machines (https://circleci.com/docs/2.0/parallelism-faster-jobs/) but i guess you mean something different?

Sorry to hear (i work for CircleCI, we're not perfect (yet) but always improving!)

There is Runner that lets you spin up your own instances: https://circleci.com/docs/2.0/runner-overview/ and you could also go "Server" which let's you run CircleCI completely on your own infra, not only the runners: https://circleci.com/docs/2.0/server-3-overview/

Let me know if you have any more questions, happy to help.

Yes, you can use your own infra with CircleCI: https://circleci.com/docs/2.0/runner-overview/

Congrats on getting Flakybot into private beta!

For people that prefer to minimize the number of moving parts, CircleCI now also has built-in Flaky test detection:

https://circleci.com/blog/introducing-test-insights-with-fla...

Of course this is coupled to our CircleCI platform, so if you want to stay agnostic for sure check out Flakybot :)

NB I work for CircleCI

Hi OP/TS! We now have a CircleCI Config SDK in early preview. You can use this SDK to generate a Dynamic Config script to checkout the files you want and generate a very specific list of the jobs and workflows you want to run.

More info on this: https://discuss.circleci.com/t/early-preview-circleci-config...

and

https://circleci.com/docs/2.0/dynamic-config/

Disclaimer: i work for CircleCI. Happy to help if there are any additional questions. We are working on some very cool improvements and optimisations to boost CircleCI into 2022, so any feedback and suggestions are very welcome!

(Disclaimer: co-founder of Vamp.io, now acquired by CircleCI)

Well-known opensource projects for "progressive delivery" are Argo Rollouts and Weave Flagger. These work in a GitOps way though. We have been developing Vamp.io to focus on the "canary releasing" and "controlled go-live" on top of K8s infra.

We're now working hard on integrating these progressive delivery Deploy&Release features nicely and seamlessly into the bigger CircleCI platform, and will shortly be opening up these features in "private beta" mode.

So expect CI/CD tools like CircleCI to be expanded with these features soon, as they provide much value to the software lifecycle.

I realise you're looking for Opensource, i respond because you also mentioned CircleCI and we're actively working on this deployment&release logic area as we speak.

RedHat has Openshift, now SUSE has Rancher.

Like Google ;P

anybody has more insights on what happened here?

Istio adds to Kubernetes:

- Automatic load balancing for HTTP, gRPC, WebSockets, and TCP traffic.

- Fine-grained control of traffic behaviour with rich routing rules, retries, fail-overs, and fault injection.

- A pluggable policy layer and configuration API supporting access controls, rate limits and quotas.

- Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress.

- Secure service-to-service communication in a cluster with strong identity-based authentication and authorization.

Istio on its own is powerful and flexible. It can also be hard to understand, setup, and manage, plus can be brittle.

(disclaimer: I'm co-founder of Vamp.io, a canary test & release system for DevOps teams that works with both HAProxy and Istio)

What Istio imho misses is a user-friendly way of setting up, managing and automating Istio configurations for microservices topologies to quickly achieve automated canary-releasing and A/B testing pipelines. Call Vamp a canary-releasing and A/B testing “control plane” for Istio/K8s if you will.

Basically the potential of service-meshes like Istio lies in "driving" it from higher-level metric/KPI-based automation systems.

We wrote several blog-posts on how to make use of Istio, starting here: https://medium.com/vamp-io/taming-istio-76fab339f685 (more blogs on Istio can be found here https://medium.com/vamp-io/tagged/istio)

Hopefully this gives some more insights in what Istio is, what it isn't, and how you can leverage it in your pipelines and architectures.

Take a look at Vamp (vamp.io) which also integrates with Kubernetes and is a programmable router based on HAproxy. It does loadbalancing, but also percentage and condition-based canary-releasing: http://vamp.io/documentation/installation/kubernetes/

(disclaimer: I'm the co-founder, looking forward to hear your thoughts and feedback!)

That's how we do it with Vamp. Interested in your thoughts: http://vamp.io/documentation/installation/kubernetes/

Founder here. Would love to hear your thoughts on how we can make Vamp better, and what kind of features we need to be focusing on while we're moving towards the Vamp 1.0 release.