Skip to content

Add Test results for v1.19 #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Test results for v1.19 #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion known-test-failures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ security architecture of vSphere and ESXi, not a fault with the product.
- [HostPath Volumes are limited in scope](#hostpath-volumes-are-limited-in-scope)
- [Only CSI-based PersistentVolumes are supported](#only-csi-based-persistentvolumes-are-supported)
- [NodePort Services are not supported](#nodeport-services-are-not-supported)
- [SchedulerPreemption is not supported](#scheduler-preemption-is-not-supported)

## Host namespace access is not possible

Expand Down Expand Up @@ -170,4 +171,21 @@ inside of the cluster.

You can also deploy an [Ingress Controller](
https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
and use layer 7 load balancing instead if you're looking to load-balance HTTP traffic.
and use layer 7 load balancing instead if you're looking to load-balance HTTP traffic.

## SchedulerPreemption is not supported

### What's the issue?

Supervisor cluster does not support Preemption based on PriorityClass during
vSphere Pod scheduling.

### What's the impact?

Preemption of lower-priority pods when higher-priority pods fail to schedule,
is not supported on the Supervisor Cluster.

### Are there workarounds?

Manually evicting lower-priority pods, to ensure there are enough resources for
higher priority pods.
Loading