apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "46562" uid: 4f01188c-149c-4375-af8d-e76263fe8dd8 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T21:46:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.262285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 1.000485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 1.094409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 1.121743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:30Z" - latency: 1.130342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:03:30Z" - latency: 1.032684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:02:30Z" - latency: 942.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:01:30Z" - latency: 1.412855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:00:30Z" - latency: 1.109815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:59:30Z" - latency: 1.106499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "48658" uid: e6ed7e1f-5bc1-42fa-8e99-7930fa9a0d94 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T21:45:30Z" message: 'load-balancer-api-external: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.925822ms message: 'load-balancer-api-external: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:30Z" - latency: 8.359221ms message: 'load-balancer-api-external: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:09:30Z" - latency: 4.412259ms message: 'load-balancer-api-external: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:30Z" - latency: 8.774741ms message: 'load-balancer-api-external: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:08:30Z" - latency: 4.121515ms message: 'load-balancer-api-external: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 9.58777ms message: 'load-balancer-api-external: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:07:30Z" - latency: 4.597246ms message: 'load-balancer-api-external: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 8.617562ms message: 'load-balancer-api-external: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:06:30Z" - latency: 4.653947ms message: 'load-balancer-api-external: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 9.903325ms message: 'load-balancer-api-external: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:05:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "48659" uid: f9df01e4-7149-47f5-9785-c0d15e646a79 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T21:45:30Z" message: 'load-balancer-api-internal: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.254363ms message: 'load-balancer-api-internal: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:30Z" - latency: 8.391811ms message: 'load-balancer-api-internal: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:09:30Z" - latency: 4.417004ms message: 'load-balancer-api-internal: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:30Z" - latency: 8.830021ms message: 'load-balancer-api-internal: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:08:30Z" - latency: 4.11024ms message: 'load-balancer-api-internal: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 9.515832ms message: 'load-balancer-api-internal: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:07:30Z" - latency: 4.610587ms message: 'load-balancer-api-internal: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 8.564228ms message: 'load-balancer-api-internal: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:06:30Z" - latency: 4.706218ms message: 'load-balancer-api-internal: tcp connection to a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 9.827943ms message: 'load-balancer-api-internal: resolved host name a722803217c1e48e8beeb175b7a6e92d-1e6cea7824027be9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:05:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-network-check-target-ip-10-0-128-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "46560" uid: af79c00c-908f-4138-a18f-f41abaeb1d99 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T21:46:30Z" message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.007751ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 2.110294ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 2.061933ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 2.000666ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:30Z" - latency: 2.006193ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:03:30Z" - latency: 1.857175ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:02:30Z" - latency: 1.634136ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:01:30Z" - latency: 1.848636ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:00:30Z" - latency: 2.027658ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:59:30Z" - latency: 1.983736ms message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-network-check-target-ip-10-0-134-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "46561" uid: b7b8f25a-0c92-4dee-861d-2c18a52bf941 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T21:46:30Z" message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.05761ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 2.231318ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 2.213384ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 2.168373ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:30Z" - latency: 2.029762ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:03:30Z" - latency: 2.09006ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:02:30Z" - latency: 2.080287ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:01:30Z" - latency: 2.172097ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:00:30Z" - latency: 1.906739ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:59:30Z" - latency: 1.98722ms message: 'network-check-target-ip-10-0-134-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-network-check-target-ip-10-0-138-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "46559" uid: 714c1517-cac1-4e65-b759-05bd4a81c681 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T21:46:30Z" message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.031µs message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 920.585µs message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 1.052813ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 1.031908ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:30Z" - latency: 1.17051ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:03:30Z" - latency: 1.144939ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:02:30Z" - latency: 858.871µs message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:01:30Z" - latency: 913.582µs message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:00:30Z" - latency: 1.070175ms message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:59:30Z" - latency: 882.01µs message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T21:58:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:39:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-193.ec2.internal uid: a22d6131-b7c2-4012-b0cc-24a1d87ef8ca resourceVersion: "48657" uid: 453b45e7-d388-4302-b619-b44fcfc7f0c1 spec: sourcePod: network-check-source-56d84b9f44-hdqmf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T21:45:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.196µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:30Z" - latency: 1.655311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:09:30Z" - latency: 762.012µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:30Z" - latency: 1.686632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:08:30Z" - latency: 1.118917ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:30Z" - latency: 2.402707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:07:30Z" - latency: 825.682µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:30Z" - latency: 1.722334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:06:30Z" - latency: 765.138µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:30Z" - latency: 2.635289ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:05:30Z" kind: List metadata: resourceVersion: ""