Adrian Chiris

Hi @amorenoz indeed i remember ! Im a bit Swamped with downstream work, will try to get this some thoughts during next week. with device info spec landing, this information...

Hi @amorenoz, Im thinking of a different approach, instead of having the information exposed across multiple environment variables per allocated device, have a single extendable environment variable per allocated device...

I must have missed the notification for your reply here Adrian. In regards to: > I thought this kind of approach was out of the table, maybe because it was...

This was discussed in today's community meeting. There is agreement to expose extended information via environment variables as this RFC proposes. it should be well document, and backward compatible so...

@bn222 we are pinning alpine version to 3.12 in Dockerfile, ran trivy on my local setup and it still hit those issues. will submit PR to update Dockerfiles.

>so this feature gate will be a new cli cmd option, and the corresponding new feature will only be evaluated when this feature gate is true? Yes, thats what i...

> Do you know of any example project that implements feature gates like Kubernetes? Id like to understand the code changes needed to turn off and off existing features. Kubernetes...

@amorenoz i think we have the same idea about implementation approach exact details can be discussed over the PR if we have a general agreement on adding support for feature...

> @adrianchiris Does this mean a singleton basically? Yep > Also, do you think that this new config should be added to the existing configMap, or should it be a...

@ian-howell does PfName selector satisfy your use-case based on community discussion we had on jul 18th ? if so we can close this PR and related issue