As the logical-cluster repository README indicates, this
project was primary created for serving in CAPI usage. Later
it can become used by other subprojects like kOps.
However, having it as a subproject creates extra work for us that
is not necessary - e.g. subproject yearly reports. After discussion
in the SIG meeting of 31.10.2023, we have agreed to move it from
a subproject to a "associated repository" of the CAPI
subproject.
A similar case for this can be seen under kubeadm -
e.g. see k/system-validators.
* initial wg lts changes
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Rename long-term-support to lts
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Update wg-lts/charter.md
Co-authored-by: Rita Zhang <rita.z.zhang@gmail.com>
* Add annual report and regular working group updates to timeline
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Update to address comments
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Address review comments
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Apply code review comment
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Add sig security to charter
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
* Update sigs.yaml
Co-authored-by: Christoph Blecker <admin@toph.ca>
* Regenerate README after sigs.yaml update
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
---------
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
Co-authored-by: Rita Zhang <rita.z.zhang@gmail.com>
Co-authored-by: Christoph Blecker <admin@toph.ca>
- Remove kube-up as a subproject. The tool correctly discovers that
we do not have OWNERS under k/k/cluster.
- Add mailing list / slack / description to projects that did not
have it.
- Rename kops -> kOps to match the project rename that happened
some time ago.
- Add more OWNERS URLs in the kubeadm subproject section. These are
not kubeadm specific repositories, but kubeadm is the best
fit given the top level SIG struct does not have OWNERS.
As discussed with the kubespray maintainers:
https://kubernetes.slack.com/archives/C2V9WJSJD/p1643716538243509
Their Zoom meeting is no longer active.
The maintainers expressed that Slack is sufficient for them
and we should remove the meeting from the calendar for the time being.
Remove the meeting from sigs.yaml
It was also removed from the SIG CL calendar.