Skip to content

Add HasNodeGroupStartedScaleUp to cluster state registry. #5221

Add HasNodeGroupStartedScaleUp to cluster state registry.

Add HasNodeGroupStartedScaleUp to cluster state registry. #5221

Triggered via pull request October 12, 2023 10:53
Status Success
Total duration 31m 17s
Artifacts

ci.yaml

on: pull_request
test-and-verify
31m 7s
test-and-verify
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/util/wait" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/apis/meta/v1" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/types" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/watch" in any of:
test-and-verify
cannot find package "k8s.io/api/autoscaling/v2" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/runtime" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/runtime/schema" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/runtime/serializer" in any of:
test-and-verify
cannot find package "k8s.io/apimachinery/pkg/util/runtime" in any of:
test-and-verify
cannot find package "k8s.io/client-go/rest" in any of:
test-and-verify
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/