apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "47218" uid: 0875fa8f-c382-4d28-a902-1ca4cfc76f60 spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T19:35:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.106234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 986.708µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 981.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 1.137933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:53:50Z" - latency: 913.767µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:52:50Z" - latency: 923.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:51:50Z" - latency: 1.161988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:50:50Z" - latency: 1.086934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:49:50Z" - latency: 1.267483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:48:50Z" - latency: 927.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "49565" uid: d34830b1-dec9-4f6a-a77e-779bafe886f5 spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T19:34:50Z" message: 'load-balancer-api-external: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.198686ms message: 'load-balancer-api-external: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:50Z" - latency: 8.002442ms message: 'load-balancer-api-external: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:58:50Z" - latency: 4.428859ms message: 'load-balancer-api-external: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:50Z" - latency: 8.962166ms message: 'load-balancer-api-external: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:57:50Z" - latency: 3.519177ms message: 'load-balancer-api-external: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 7.913618ms message: 'load-balancer-api-external: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:56:50Z" - latency: 4.87897ms message: 'load-balancer-api-external: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 9.56577ms message: 'load-balancer-api-external: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:55:50Z" - latency: 4.62951ms message: 'load-balancer-api-external: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 8.321743ms message: 'load-balancer-api-external: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:54:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "49564" uid: 2c182973-7ea5-4aa3-82d7-bec0036689e7 spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T19:34:50Z" message: 'load-balancer-api-internal: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.186578ms message: 'load-balancer-api-internal: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:50Z" - latency: 7.920564ms message: 'load-balancer-api-internal: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:58:50Z" - latency: 3.464522ms message: 'load-balancer-api-internal: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:50Z" - latency: 8.876215ms message: 'load-balancer-api-internal: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:57:50Z" - latency: 3.461544ms message: 'load-balancer-api-internal: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 7.830193ms message: 'load-balancer-api-internal: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:56:50Z" - latency: 4.906263ms message: 'load-balancer-api-internal: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 9.494217ms message: 'load-balancer-api-internal: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:55:50Z" - latency: 4.942035ms message: 'load-balancer-api-internal: tcp connection to a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 8.280148ms message: 'load-balancer-api-internal: resolved host name a25d3a01a6cc04a0280d1d40029f0f1a-8fd91a6eeddfc0d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T19:54:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-network-check-target-ip-10-0-129-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "47215" uid: ac9603d1-44ee-4995-acad-c812adcdc8b5 spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T19:35:50Z" message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.666µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 1.197587ms message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 919.422µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 888.249µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:53:50Z" - latency: 809.769µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:52:50Z" - latency: 1.056374ms message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:51:50Z" - latency: 846.832µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:50:50Z" - latency: 1.296189ms message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:49:50Z" - latency: 844.463µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:48:50Z" - latency: 966.941µs message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-network-check-target-ip-10-0-137-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "47216" uid: b6042abd-e524-4107-b995-76583ba4e6ad spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T19:35:50Z" message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.218655ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 2.047219ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 2.025762ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 2.308461ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:53:50Z" - latency: 2.01229ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:52:50Z" - latency: 2.20643ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:51:50Z" - latency: 2.297074ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:50:50Z" - latency: 2.388787ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:49:50Z" - latency: 2.299983ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:48:50Z" - latency: 2.112092ms message: 'network-check-target-ip-10-0-137-13: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-network-check-target-ip-10-0-138-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "47217" uid: c57abedb-5776-4435-94cb-5e9e6fc57cc2 spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T19:35:50Z" message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.455316ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 2.331048ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 2.387456ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 2.294626ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:53:50Z" - latency: 2.299218ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:52:50Z" - latency: 2.380373ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:51:50Z" - latency: 2.586366ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:50:50Z" - latency: 2.481953ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:49:50Z" - latency: 2.315157ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:48:50Z" - latency: 2.284837ms message: 'network-check-target-ip-10-0-138-80: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:28:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-220-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-220.ec2.internal uid: d30db575-3ad6-4e6e-9592-bc35820aa028 resourceVersion: "49562" uid: ff5e5232-f91c-4d4c-94c3-248c707e65f0 spec: sourcePod: network-check-source-dbd9cf844-wtw8z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T19:34:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.659µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:50Z" - latency: 2.066076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T19:58:50Z" - latency: 802.749µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:50Z" - latency: 1.756671ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T19:57:50Z" - latency: 865.858µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:56:50Z" - latency: 1.816585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T19:56:50Z" - latency: 750.447µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:55:50Z" - latency: 1.859259ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T19:55:50Z" - latency: 893.794µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:54:50Z" - latency: 1.93622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T19:54:50Z" kind: List metadata: resourceVersion: ""