apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "71601" uid: 833851e5-0426-4d83-ab9d-9619501a4840 spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T01:07:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.162654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:49:56Z" - latency: 830.031µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 1.101681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 1.303528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 2.012019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 1.134019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 922.488µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:43:56Z" - latency: 1.107817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:42:56Z" - latency: 1.073507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:41:56Z" - latency: 937.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:40:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "70663" uid: 1f689f58-7ace-49bb-bbc1-9991fc08e8d3 spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T01:06:56Z" message: 'load-balancer-api-external: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.963319ms message: 'load-balancer-api-external: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 7.747097ms message: 'load-balancer-api-external: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:48:56Z" - latency: 3.573482ms message: 'load-balancer-api-external: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 7.523958ms message: 'load-balancer-api-external: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:47:56Z" - latency: 4.388193ms message: 'load-balancer-api-external: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 6.816592ms message: 'load-balancer-api-external: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:46:56Z" - latency: 3.916104ms message: 'load-balancer-api-external: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 10.942876ms message: 'load-balancer-api-external: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:45:56Z" - latency: 4.11269ms message: 'load-balancer-api-external: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 6.925989ms message: 'load-balancer-api-external: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:44:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "70662" uid: b6d78709-1db8-476f-8ede-cdbaa3e52c6a spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T01:06:56Z" message: 'load-balancer-api-internal: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.877445ms message: 'load-balancer-api-internal: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 7.684007ms message: 'load-balancer-api-internal: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:48:56Z" - latency: 3.630295ms message: 'load-balancer-api-internal: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 7.588814ms message: 'load-balancer-api-internal: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:47:56Z" - latency: 5.410955ms message: 'load-balancer-api-internal: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 6.913467ms message: 'load-balancer-api-internal: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:46:56Z" - latency: 4.863559ms message: 'load-balancer-api-internal: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 10.88495ms message: 'load-balancer-api-internal: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:45:56Z" - latency: 4.618138ms message: 'load-balancer-api-internal: tcp connection to a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 7.007809ms message: 'load-balancer-api-internal: resolved host name a04db2bce41484714a0164a0e536bb71-05b0626d74cc0242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T01:44:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-network-check-target-ip-10-0-129-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "71600" uid: c30afa28-200e-487f-aba3-b62f92377a4b spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T01:07:56Z" message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.519106ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:49:56Z" - latency: 2.601983ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 2.712866ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 2.054339ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 2.308759ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 2.263793ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 2.419791ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:43:56Z" - latency: 2.373053ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:42:56Z" - latency: 2.422974ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:41:56Z" - latency: 2.01544ms message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:40:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-network-check-target-ip-10-0-132-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "71598" uid: 1f872f6e-4e4b-4c58-bab1-764418d1001c spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T01:07:56Z" message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.575µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:49:56Z" - latency: 1.84213ms message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 1.130033ms message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 890.6µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 943.527µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 1.263914ms message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 940.122µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:43:56Z" - latency: 969.733µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:42:56Z" - latency: 899.354µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:41:56Z" - latency: 833.362µs message: 'network-check-target-ip-10-0-132-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:40:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-network-check-target-ip-10-0-139-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "71599" uid: 8d081b3b-4879-4361-87b6-c02d7dd583f0 spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T01:07:56Z" message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.600697ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:49:56Z" - latency: 2.567731ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 2.544831ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 2.402093ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 2.519769ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 2.407796ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 2.305253ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:43:56Z" - latency: 2.47841ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:42:56Z" - latency: 2.52458ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:41:56Z" - latency: 2.154803ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:40:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T01:00:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-136-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-136.ec2.internal uid: 718168ee-22fe-46e7-b856-1eef81c53e51 resourceVersion: "70661" uid: e3113df3-294c-4194-af46-b31b0e4add39 spec: sourcePod: network-check-source-7d88cb55d8-vvwkz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T01:06:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.178µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:48:56Z" - latency: 2.722033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:48:56Z" - latency: 1.217121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:47:56Z" - latency: 2.161939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:47:56Z" - latency: 906.118µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:46:56Z" - latency: 1.808258ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:46:56Z" - latency: 859.733µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:45:56Z" - latency: 2.063231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:45:56Z" - latency: 905.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T01:44:56Z" - latency: 1.689104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T01:44:56Z" kind: List metadata: resourceVersion: ""