cncf-toc@lists.cncf.io

Home Messages Hashtags Subgroups

Messages

Between

and

Re: updating what it means to be "Cloud Native"

Deliberately vague. Yes, it could include the platform, such as Kubernetes. I don't know that we're ready to draw a firm boundary yet. Cloud Native is still somewhat aspirational.

By Brian Grant · #1635 ·

Re: updating what it means to be "Cloud Native"

This is much, much better!

By Drew Rapenchuk <drapenchuk@...> · #1634 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 (non-binding)

By Spike Curtis · #1633 ·

Re: updating what it means to be "Cloud Native"

Not at all. Please do! I shared them so they could be incorporated I agree. Many things can claim to be "scalable" but every design decision has trade-offs. How you get to scalability

By Justin Garrison <justinleegarrison@...> · #1632 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 (non-binding)

By Olivier Mallassi <olivier.mallassi@...> · #1631 ·

Re: [VOTE] SPIFFE project proposal (inception)

By Ramses Martinez <ramses_martinez@...> · #1630 ·

Re: updating what it means to be "Cloud Native"

As much as I'm a strong proponent of declarative configuration and APIs (and declarative APIs :-)), I agree that they are implementation techniques. I think we should provides examples of such

By Brian Grant · #1629 ·

Re: updating what it means to be "Cloud Native"

I prefer the engineered attributes: Operable Observable Elastic Resilient AgileOver the end goals: Scalable Durable Continuous Since I think some indication of strategy/technique is needed in order

By Brian Grant · #1628 ·

Re: updating what it means to be "Cloud Native"

Great discussion. Thanks! Do you mind if we incorporate some/all of them? ChrisA also pointed out that Schedule A at the bottom of the charter also needs to be similarly updated. My current thinking

By Brian Grant · #1627 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 non binding

By Justin Cormack · #1626 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 (non-binding) -- Michael Fertik michael@... DISCLAIMER Any private opportunity discussed in this email or its attachments is being presented to you because you have expressed an interest in such

By Michael Fertik · #1625 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 non-binding

By Kevin Lynch · #1624 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 non-binding Andrew Randall Tigera

By Andrew Randall · #1623 ·

Re: [VOTE] SPIFFE project proposal (inception)

0 non-binding I think the spec is very interesting and necessary but I feel like it, and associated example tooling (SPIRE), may be too early for even inception level -- Justin

By Justin Garrison <justinleegarrison@...> · #1622 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 binding

By Brian Grant · #1621 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 (non-binding) Alan Fraser CREDIT SUISSE Information Technology | Core Eng - Engineering Solutions - NY, VIAD 32

By Alan <alan.fraser@...> · #1620 ·

Re: [VOTE] SPIFFE project proposal (inception)

-1 binding. I would rather see this mature for a while.

By Camille Fournier · #1619 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 (non-binding) Ramkumar Kb Lead Engineer, APAC-PB-IT Channels +65 6212 8403 (*650 8403) ============================================================================== Please access the

By Kb, Ramkumar <ramkumar.kalpathy@...> · #1618 ·

Re: [VOTE] SPIFFE project proposal (inception)

I’m +1 only the spec. -1 anything else. On Thu, Feb 1, 2018 at 17:34 Thangavelu, Kapil via Lists.Cncf.Io <kapil.thangavelu=capitalone.com@...> wrote: -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A

By me@... · #1617 ·

Re: [VOTE] SPIFFE project proposal (inception)

+1 (non-binding)

By Thangavelu, Kapil · #1616 ·

6361 - 6380 of 7995

Home Hashtags Subgroups Terms