apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "71369" uid: 410e62d6-579e-4c5b-bfcd-d9bb94bb9163 spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-03T16:15:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.100289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:57:17Z" - latency: 1.35501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:56:17Z" - latency: 1.381523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:55:17Z" - latency: 993.239µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:54:17Z" - latency: 1.041407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:53:17Z" - latency: 1.594459ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:52:17Z" - latency: 1.867954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:51:17Z" - latency: 1.331687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:50:17Z" - latency: 1.571605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:49:17Z" - latency: 1.298123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:48:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "76717" uid: c9378cc7-cff3-4935-987c-85a7bcb3e57c spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-03T16:14:17Z" message: 'load-balancer-api-external: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.102045ms message: 'load-balancer-api-external: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:02:17Z" - latency: 7.704876ms message: 'load-balancer-api-external: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T17:02:17Z" - latency: 5.863829ms message: 'load-balancer-api-external: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:01:17Z" - latency: 12.054667ms message: 'load-balancer-api-external: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T17:01:17Z" - latency: 6.243919ms message: 'load-balancer-api-external: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:00:17Z" - latency: 8.853115ms message: 'load-balancer-api-external: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T17:00:17Z" - latency: 4.456549ms message: 'load-balancer-api-external: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:59:17Z" - latency: 8.283567ms message: 'load-balancer-api-external: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T16:59:17Z" - latency: 3.019821ms message: 'load-balancer-api-external: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:58:17Z" - latency: 12.766815ms message: 'load-balancer-api-external: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T16:58:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "76718" uid: 54e3fc4f-df7a-47e8-a574-84578f88c9ce spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-03T16:14:17Z" message: 'load-balancer-api-internal: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.89923ms message: 'load-balancer-api-internal: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:02:17Z" - latency: 7.676358ms message: 'load-balancer-api-internal: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T17:02:17Z" - latency: 6.196517ms message: 'load-balancer-api-internal: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:01:17Z" - latency: 12.17367ms message: 'load-balancer-api-internal: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T17:01:17Z" - latency: 5.559957ms message: 'load-balancer-api-internal: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:00:17Z" - latency: 8.828004ms message: 'load-balancer-api-internal: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T17:00:17Z" - latency: 4.429327ms message: 'load-balancer-api-internal: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:59:17Z" - latency: 8.395482ms message: 'load-balancer-api-internal: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T16:59:17Z" - latency: 3.11663ms message: 'load-balancer-api-internal: tcp connection to a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:58:17Z" - latency: 12.728012ms message: 'load-balancer-api-internal: resolved host name a2b997563785244029c3e9260c6b0492-c7d86bba6f3cab58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-03T16:58:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-network-check-target-ip-10-0-133-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "71366" uid: b25a3077-91f2-46d0-9088-1bf8a1e60988 spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-03T16:15:17Z" message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.303457ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:57:17Z" - latency: 1.031375ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:56:17Z" - latency: 1.044902ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:55:17Z" - latency: 945.748µs message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:54:17Z" - latency: 998.18µs message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:53:17Z" - latency: 1.088659ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:52:17Z" - latency: 1.222874ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:51:17Z" - latency: 1.399035ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:50:17Z" - latency: 1.695711ms message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:49:17Z" - latency: 935.151µs message: 'network-check-target-ip-10-0-133-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:48:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-network-check-target-ip-10-0-138-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "71368" uid: af265322-475c-4d7d-abfa-7bbcd446a0c4 spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-03T16:15:17Z" message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.034206ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:57:17Z" - latency: 2.411065ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:56:17Z" - latency: 2.500978ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:55:17Z" - latency: 2.498492ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:54:17Z" - latency: 2.432456ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:53:17Z" - latency: 2.361456ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:52:17Z" - latency: 2.414561ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:51:17Z" - latency: 2.75848ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:50:17Z" - latency: 2.224314ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:49:17Z" - latency: 2.625245ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:48:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-network-check-target-ip-10-0-142-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "71367" uid: 00815b66-1a61-434c-b573-c7497d92ab7d spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-03T16:15:17Z" message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212275ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:57:17Z" - latency: 2.196884ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:56:17Z" - latency: 2.41469ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:55:17Z" - latency: 2.908793ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:54:17Z" - latency: 2.37245ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:53:17Z" - latency: 2.410701ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:52:17Z" - latency: 1.862961ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:51:17Z" - latency: 2.680487ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:50:17Z" - latency: 2.243947ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:49:17Z" - latency: 2.482011ms message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:48:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-03T16:08:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-47.ec2.internal uid: b984cee4-976c-43ec-a11e-077e564472ba resourceVersion: "76716" uid: a63924bb-5c78-4ec7-ba99-54969949b3f5 spec: sourcePod: network-check-source-65bdbbff45-kmm5q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-03T16:14:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.478µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:02:17Z" - latency: 2.404485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-03T17:02:17Z" - latency: 1.522197ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:01:17Z" - latency: 2.066615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-03T17:01:17Z" - latency: 915.264µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-03T17:00:17Z" - latency: 2.0099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-03T17:00:17Z" - latency: 1.16993ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:59:17Z" - latency: 1.997038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-03T16:59:17Z" - latency: 910.208µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-03T16:58:17Z" - latency: 1.770139ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-03T16:58:17Z" kind: List metadata: resourceVersion: ""