apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "44323" uid: 83a98c17-58ed-418c-8093-635a2c3afbc4 spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T11:29:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.257535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 1.133857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 830.677µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 1.041846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:47:22Z" - latency: 1.348441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:46:22Z" - latency: 998.525µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:45:22Z" - latency: 1.179445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:44:22Z" - latency: 1.172614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:43:22Z" - latency: 1.241624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:42:22Z" - latency: 955.045µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:41:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "46426" uid: feffc8fe-f476-413a-a96a-e6a7bafbb8bf spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T11:28:22Z" message: 'load-balancer-api-external: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.962098ms message: 'load-balancer-api-external: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:52:22Z" - latency: 8.321377ms message: 'load-balancer-api-external: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:52:22Z" - latency: 5.443251ms message: 'load-balancer-api-external: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:51:22Z" - latency: 8.412125ms message: 'load-balancer-api-external: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:51:22Z" - latency: 6.284053ms message: 'load-balancer-api-external: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 8.28939ms message: 'load-balancer-api-external: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:50:22Z" - latency: 4.996205ms message: 'load-balancer-api-external: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 8.506314ms message: 'load-balancer-api-external: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:49:22Z" - latency: 5.025424ms message: 'load-balancer-api-external: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 9.444727ms message: 'load-balancer-api-external: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:48:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "46425" uid: d0660379-22dc-40d5-b495-8f7977abe0f9 spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T11:28:22Z" message: 'load-balancer-api-internal: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.951511ms message: 'load-balancer-api-internal: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:52:22Z" - latency: 8.369969ms message: 'load-balancer-api-internal: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:52:22Z" - latency: 5.456164ms message: 'load-balancer-api-internal: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:51:22Z" - latency: 8.514424ms message: 'load-balancer-api-internal: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:51:22Z" - latency: 6.204975ms message: 'load-balancer-api-internal: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 8.424127ms message: 'load-balancer-api-internal: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:50:22Z" - latency: 4.998327ms message: 'load-balancer-api-internal: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 8.624208ms message: 'load-balancer-api-internal: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:49:22Z" - latency: 4.942527ms message: 'load-balancer-api-internal: tcp connection to af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 9.498818ms message: 'load-balancer-api-internal: resolved host name af644ae3385cd4b58a990de9526a45f8-90740c0de0b595f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T11:48:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-network-check-target-ip-10-0-130-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "44319" uid: d90f817f-aabc-47dc-b550-7f4f85620a4c spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T11:29:22Z" message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.903µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 973.321µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 945.798µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 960.158µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:47:22Z" - latency: 903.165µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:46:22Z" - latency: 901.489µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:45:22Z" - latency: 1.133053ms message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:44:22Z" - latency: 985.115µs message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:43:22Z" - latency: 1.000034ms message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:42:22Z" - latency: 1.024629ms message: 'network-check-target-ip-10-0-130-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:41:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-network-check-target-ip-10-0-138-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "44320" uid: bc61d909-eef4-47e9-b837-eb6c2c20591a spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T11:29:22Z" message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.117743ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 2.020507ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 1.958442ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 2.150529ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:47:22Z" - latency: 1.871086ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:46:22Z" - latency: 2.056633ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:45:22Z" - latency: 1.982401ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:44:22Z" - latency: 1.998339ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:43:22Z" - latency: 1.985218ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:42:22Z" - latency: 2.109411ms message: 'network-check-target-ip-10-0-138-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:41:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-network-check-target-ip-10-0-143-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "44322" uid: 36cfab4d-69ca-43ab-85ab-cb047df00327 spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T11:29:22Z" message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.304165ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 2.089393ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 2.383903ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 1.969038ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:47:22Z" - latency: 2.331904ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:46:22Z" - latency: 2.268351ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:45:22Z" - latency: 1.96243ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:44:22Z" - latency: 2.045169ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:43:22Z" - latency: 2.353674ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:42:22Z" - latency: 2.365623ms message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:41:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T11:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-135.ec2.internal uid: c4fa99fe-4891-435c-87fb-f21247c5536c resourceVersion: "46423" uid: e0e4bc55-c5ed-4c80-bea7-e6de99718320 spec: sourcePod: network-check-source-dbd9cf844-7kqxf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T11:28:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022555ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:52:22Z" - latency: 1.856503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T11:52:22Z" - latency: 993.219µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:51:22Z" - latency: 1.693289ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T11:51:22Z" - latency: 885.968µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:50:22Z" - latency: 1.732083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T11:50:22Z" - latency: 823.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:49:22Z" - latency: 1.691579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T11:49:22Z" - latency: 687.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T11:48:22Z" - latency: 2.423853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T11:48:22Z" kind: List metadata: resourceVersion: ""