4 ms·

How long do you expect CDK to lag behind upstream Kubernetes releases? So far it's been pretty tight, but I'm curious about what sort of expectation you have he

by arjie 10y ago

How long do you expect CDK to lag behind upstream Kubernetes releases? So far it's been pretty tight, but I'm curious about what sort of expectation you have here.

jcastro 10y ago
Right now we're about 3-5 days behind an upstream release, so right now we're at 1.5.2.
marcoceppi 10y ago
We're still "beta" so we have been able to release within 10 after upstream. With recent updates to our build/ci process, we're able to constantly test master. This means we can bless releases days after being cut. Expect GA for CDK around 1.6.0 release time, which we will be driving for release blessed within five business days of upstream.
- bonzini 10y ago
  > five business days of upstream So you do not do any integration testing, or for that matter hardly any testing at all?
  - andrewsomething 10y ago
    > we're able to constantly test master You seemed to have missed this.
    - bonzini 10y ago
      It also said "With recent updates to our build/ci process" but there is more to testing than continuous integration, especially for something as complex as Kubernetes. In particular, continuous integration can run regression tests but how many bugs will it find due to interactions between features?
  - marcoceppi 10y ago
    We don't begin integration testing at day 0 of release, we are constantly integration testing. That said, five days is a goal of ours, not a hard deadline or SLA. An example of this was the 1.5.2. This came out 8 or 9 days after upstream because we had failing integration and e2e tests starting a few days before release and it took some time to hunt down, address, and make sure it was an issue with how we're deploying k8s and not k8s itself. Hopefully that clarifies how we're able to to stride towards that goal. To be honest, testing like this is as much and art as it is a science and it's taken quite a while to get to where we are now (and admittedly, still a ways to go until we're satisfied). Let me know if have any other questions!

by arjie 10y ago

How long do you expect CDK to lag behind upstream Kubernetes releases? So far it's been pretty tight, but I'm curious about what sort of expectation you have here.

jcastro 10y ago

Right now we're about 3-5 days behind an upstream release, so right now we're at 1.5.2.

marcoceppi 10y ago

We're still "beta" so we have been able to release within 10 after upstream. With recent updates to our build/ci process, we're able to constantly test master. This means we can bless releases days after being cut. Expect GA for CDK around 1.6.0 release time, which we will be driving for release blessed within five business days of upstream.

bonzini 10y ago
> five business days of upstream So you do not do any integration testing, or for that matter hardly any testing at all?
- andrewsomething 10y ago
  > we're able to constantly test master You seemed to have missed this.
  - bonzini 10y ago
    It also said "With recent updates to our build/ci process" but there is more to testing than continuous integration, especially for something as complex as Kubernetes. In particular, continuous integration can run regression tests but how many bugs will it find due to interactions between features?
- marcoceppi 10y ago
  We don't begin integration testing at day 0 of release, we are constantly integration testing. That said, five days is a goal of ours, not a hard deadline or SLA. An example of this was the 1.5.2. This came out 8 or 9 days after upstream because we had failing integration and e2e tests starting a few days before release and it took some time to hunt down, address, and make sure it was an issue with how we're deploying k8s and not k8s itself. Hopefully that clarifies how we're able to to stride towards that goal. To be honest, testing like this is as much and art as it is a science and it's taken quite a while to get to where we are now (and admittedly, still a ways to go until we're satisfied). Let me know if have any other questions!