killianmuldoon

Results 44 issues of killianmuldoon

The `clusterctl` upgrade tests have been significantly flaky in the last couple of weeks, with flakes occurring on `main` `release-1.4` and `release-1.5`. The flakes are occurring across many forms of...

help wanted
kind/flake
area/clusterctl
triage/accepted
area/e2e-testing

In the CAPI e2e test framework currently the `kubectl` binary is called to apply yamls when creating Clusters. This would improve error reporting from this function which may help to...

help wanted
triage/accepted
area/e2e-testing

**What steps did you take and what happened:** Ran `clusterctl init` after a new tag (v1.3.2) for the repo was created, but before a new release corresponding to the tag...

help wanted
kind/bug
area/clusterctl
triage/accepted

Hi folks - I just wanted to flag that this repo no longer works with a supported version of Cluster API. CAPI currently supports only v1beta1 APIs and only CAPI...

There's a number labels in the CAPV codebase related to older APIVersions that should be removed along with the code that handles transitioning them. We have: - Added in https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/1486...

area/supervisor
area/govmomi

[This is a tracking issue for similar work in upstream Cluster API](https://github.com/kubernetes-sigs/cluster-api/issues/9434) CAPV should add tests to ensure that finalizers added to objects can be correctly re-added if they are...

The ownerReference chain in Cluster API provider for vSphere should be consistent with expectations in Kubernetes and Cluster API. Cluster API has ownerReference guidelines documented at https://cluster-api.sigs.k8s.io/reference/owner_references Tasks: - [x]...

help wanted

Drop the Cluster API targets from CNCF fuzzing. Currently the fuzzers for CAPI aren't building and are unmaintained. This has been the case for some time. Tracking https://github.com/kubernetes-sigs/cluster-api/issues/9548 oss-fuzz PR:...

It would be useful to have klog reference format that includes all of the information about a resource required to identify it - i.e. Group, Version, Kind, Namespace and Name....

kind/feature
needs-triage

Cluster API should use "current" instead of "replicas" in CLI output to express the number of instances of an object in a scalable resource. With https://github.com/kubernetes-sigs/cluster-api/pull/6164 we're adding `desired` to...

help wanted
priority/important-longterm
kind/api-change
area/api
triage/accepted