search

falcosecurity / cncf-green-review-testing

Falco configurations intended for testing with the CNCF Green Reviews Working Group
Apache License 2.0
1 stars 2 forks source link

Versioning #1

Open incertum opened 6 months ago

incertum commented 6 months ago

Initial versioning idea captured in https://github.com/falcosecurity/cncf-green-review-testing?tab=readme-ov-file#versioning

The respective CONFIG_VERSION environment variable within the daemonset deployment contains the semver-compatible version of the testbed setup. We inject it (as a suffix) into the FALCO_HOSTNAME environment variable to maintain a version record extending beyond the Falco version in the native Falco metrics. Every merge into the main branch necessitates a (mostly minor) version increment.

TBD if this is sufficient or if we simply have a better idea.

Lastly, since the CNCF TAGs repo will put a watch on the main branch, every config change and merge is considered a versioning bump on our end. However, since the testbed is not yet "live" we don't need to bump versioning as we tweak and complete deployment details. Once the testbed is officially "live" we need to be reminded of the version bumps.

poiana commented 1 month ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

poiana commented 4 weeks ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten