apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "69749" uid: b835e1d7-2bc9-4386-91e9-5a5eaa41086c spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T14:46:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:28:33Z" - latency: 1.43214ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 966.244µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 1.049811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 1.367916ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 1.045761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 1.299955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:22:33Z" - latency: 1.087256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:21:33Z" - latency: 932.364µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:20:33Z" - latency: 1.347311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "68649" uid: 4063ee6d-fdcf-46f9-994b-40537f692808 spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T14:45:33Z" message: 'load-balancer-api-external: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.420008ms message: 'load-balancer-api-external: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 6.951233ms message: 'load-balancer-api-external: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:27:33Z" - latency: 4.132282ms message: 'load-balancer-api-external: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 9.3791ms message: 'load-balancer-api-external: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:26:33Z" - latency: 4.898549ms message: 'load-balancer-api-external: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 8.445456ms message: 'load-balancer-api-external: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:25:33Z" - latency: 4.989212ms message: 'load-balancer-api-external: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 8.375252ms message: 'load-balancer-api-external: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:24:33Z" - latency: 5.494964ms message: 'load-balancer-api-external: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 8.407849ms message: 'load-balancer-api-external: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:23:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "68650" uid: 10500edf-0e42-4dcb-a567-ca9b9b6894eb spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T14:45:33Z" message: 'load-balancer-api-internal: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.927477ms message: 'load-balancer-api-internal: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 7.339695ms message: 'load-balancer-api-internal: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:27:33Z" - latency: 3.999696ms message: 'load-balancer-api-internal: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 9.325231ms message: 'load-balancer-api-internal: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:26:33Z" - latency: 4.70585ms message: 'load-balancer-api-internal: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 8.480434ms message: 'load-balancer-api-internal: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:25:33Z" - latency: 4.958432ms message: 'load-balancer-api-internal: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 8.431966ms message: 'load-balancer-api-internal: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:24:33Z" - latency: 5.538523ms message: 'load-balancer-api-internal: tcp connection to a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 8.485835ms message: 'load-balancer-api-internal: resolved host name a722822dbce6c40d78d4ab28fe7b272f-266020fdc382437e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T15:23:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-network-check-target-ip-10-0-132-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "69748" uid: 3c1346e8-cb2c-481a-bb84-80aa532e6679 spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T14:46:33Z" message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.996732ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:28:33Z" - latency: 2.265825ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 2.243432ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 1.899118ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 1.956225ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 2.171822ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 2.353234ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:22:33Z" - latency: 2.056398ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:21:33Z" - latency: 2.250015ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:20:33Z" - latency: 2.203543ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-network-check-target-ip-10-0-136-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "69747" uid: 4aba117f-c902-41ce-90dc-d90818405ddd spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T14:46:33Z" message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.574977ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:28:33Z" - latency: 1.345121ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 1.021645ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 1.000256ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 1.353776ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 1.213236ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 1.572193ms message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:22:33Z" - latency: 977.771µs message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:21:33Z" - latency: 863.201µs message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:20:33Z" - latency: 879.064µs message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-network-check-target-ip-10-0-142-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "69746" uid: 5184e372-8818-43c3-8daf-2d6316314f26 spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T14:46:33Z" message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.912683ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:28:33Z" - latency: 2.201772ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 1.982236ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 1.965908ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 2.016685ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 1.893597ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 1.821824ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:22:33Z" - latency: 2.005444ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:21:33Z" - latency: 1.813794ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:20:33Z" - latency: 1.907876ms message: 'network-check-target-ip-10-0-142-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:19:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T14:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-196-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-196.ec2.internal uid: d36857a3-e7be-4668-b0d5-6f0981f31d7e resourceVersion: "68648" uid: e0766c62-bcb7-4697-9306-27754972a1d8 spec: sourcePod: network-check-source-7d88cb55d8-lbmwl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T14:45:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.01485ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:27:33Z" - latency: 2.607567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:27:33Z" - latency: 815.834µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:26:33Z" - latency: 2.371379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:26:33Z" - latency: 809.759µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:25:33Z" - latency: 1.9981ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:25:33Z" - latency: 965.912µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:24:33Z" - latency: 1.658306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:24:33Z" - latency: 934.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T15:23:33Z" - latency: 1.964083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T15:23:33Z" kind: List metadata: resourceVersion: ""