apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "47056" uid: fa15562f-c6db-4953-b30d-7a09fae05c44 spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T23:37:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.466µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 996.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 809.918µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 1.203143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:55:53Z" - latency: 1.054857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:54:53Z" - latency: 879.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:53:53Z" - latency: 1.153734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:52:53Z" - latency: 779.054µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:51:53Z" - latency: 1.108863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:50:53Z" - latency: 1.21982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:49:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "49210" uid: fa9450a3-6c8b-4a50-b7b8-3b75c31dca1d spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T23:36:53Z" message: 'load-balancer-api-external: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.8473ms message: 'load-balancer-api-external: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-04T00:00:53Z" - latency: 8.897251ms message: 'load-balancer-api-external: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-04T00:00:53Z" - latency: 4.654505ms message: 'load-balancer-api-external: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:59:53Z" - latency: 8.483247ms message: 'load-balancer-api-external: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:59:53Z" - latency: 3.659977ms message: 'load-balancer-api-external: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 9.371758ms message: 'load-balancer-api-external: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:58:53Z" - latency: 4.910118ms message: 'load-balancer-api-external: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 9.101466ms message: 'load-balancer-api-external: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:57:53Z" - latency: 4.692651ms message: 'load-balancer-api-external: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 8.319348ms message: 'load-balancer-api-external: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:56:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "49209" uid: d2562180-bd0b-4c56-a176-bbaf0d28758b spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T23:36:53Z" message: 'load-balancer-api-internal: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.858457ms message: 'load-balancer-api-internal: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-04T00:00:53Z" - latency: 8.830431ms message: 'load-balancer-api-internal: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-04T00:00:53Z" - latency: 4.277455ms message: 'load-balancer-api-internal: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:59:53Z" - latency: 8.443739ms message: 'load-balancer-api-internal: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:59:53Z" - latency: 3.699091ms message: 'load-balancer-api-internal: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 9.331987ms message: 'load-balancer-api-internal: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:58:53Z" - latency: 4.932989ms message: 'load-balancer-api-internal: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 9.076884ms message: 'load-balancer-api-internal: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:57:53Z" - latency: 4.689043ms message: 'load-balancer-api-internal: tcp connection to afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 8.238275ms message: 'load-balancer-api-internal: resolved host name afe645cdd19144aa4921fa884fb7da0e-904e0d52776dd905.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:56:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-network-check-target-ip-10-0-131-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "47055" uid: 715acae8-ae35-4238-b4e3-cf329854d387 spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T23:37:53Z" message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 805.25µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 858.909µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 658.989µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 810.312µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:55:53Z" - latency: 1.480886ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:54:53Z" - latency: 724.625µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:53:53Z" - latency: 1.310421ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:52:53Z" - latency: 838.257µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:51:53Z" - latency: 797.287µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:50:53Z" - latency: 932.417µs message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:49:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-network-check-target-ip-10-0-135-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "47053" uid: 5e4d286f-495e-4f6a-a382-7c133d3bcd99 spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T23:37:53Z" message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.928423ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 1.799299ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 2.08688ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 2.20221ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:55:53Z" - latency: 2.018816ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:54:53Z" - latency: 1.576471ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:53:53Z" - latency: 1.981298ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:52:53Z" - latency: 2.074869ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:51:53Z" - latency: 2.290407ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:50:53Z" - latency: 2.222853ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:49:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-network-check-target-ip-10-0-137-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "47054" uid: 586c516a-e339-487c-8d1a-4337c304815a spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T23:37:53Z" message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.953757ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 1.932935ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 2.038179ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 2.261257ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:55:53Z" - latency: 2.108154ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:54:53Z" - latency: 1.90228ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:53:53Z" - latency: 2.043294ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:52:53Z" - latency: 2.400653ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:51:53Z" - latency: 2.226253ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:50:53Z" - latency: 2.343906ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:49:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:30:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-117.ec2.internal uid: 3034f00a-de47-4467-a6cd-e43e7a6c4369 resourceVersion: "49207" uid: 0cbe58dc-e64b-4ea4-ba60-32181ae4c12d spec: sourcePod: network-check-source-dbd9cf844-2f7zd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T23:36:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 765.069µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-04T00:00:53Z" - latency: 1.798059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-04T00:00:53Z" - latency: 892.427µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:59:53Z" - latency: 1.841751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:59:53Z" - latency: 996.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:58:53Z" - latency: 1.651882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:58:53Z" - latency: 793.708µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:57:53Z" - latency: 1.8538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:57:53Z" - latency: 890.597µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:56:53Z" - latency: 2.014733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:56:53Z" kind: List metadata: resourceVersion: ""