apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60609" uid: 3a8bab4b-4811-4790-8fcc-3109c32f5eb2 spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T12:30:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.103183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 819.475µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 1.42465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 840.08µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 1.000656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 1.044513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:00:33Z" - latency: 955.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:33Z" - latency: 1.278297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:33Z" - latency: 1.006978ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:33Z" - latency: 1.188757ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60608" uid: a91ca587-0f87-460c-821c-18fcdf61dbc6 spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T12:29:33Z" message: 'load-balancer-api-external: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 13.726133ms message: 'load-balancer-api-external: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 7.97556ms message: 'load-balancer-api-external: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:05:33Z" - latency: 4.319526ms message: 'load-balancer-api-external: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 9.022774ms message: 'load-balancer-api-external: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:04:33Z" - latency: 5.025312ms message: 'load-balancer-api-external: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 6.398579ms message: 'load-balancer-api-external: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:03:33Z" - latency: 4.772381ms message: 'load-balancer-api-external: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 7.169402ms message: 'load-balancer-api-external: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:02:33Z" - latency: 4.145839ms message: 'load-balancer-api-external: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 7.119287ms message: 'load-balancer-api-external: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:01:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60610" uid: dc02f3e4-924b-4cba-9509-ee1fad179366 spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T12:29:33Z" message: 'load-balancer-api-internal: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.365085ms message: 'load-balancer-api-internal: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 7.994228ms message: 'load-balancer-api-internal: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:05:33Z" - latency: 7.816753ms message: 'load-balancer-api-internal: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 9.068675ms message: 'load-balancer-api-internal: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:04:33Z" - latency: 4.974098ms message: 'load-balancer-api-internal: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 6.351704ms message: 'load-balancer-api-internal: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:03:33Z" - latency: 4.803529ms message: 'load-balancer-api-internal: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 7.261145ms message: 'load-balancer-api-internal: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:02:33Z" - latency: 3.76667ms message: 'load-balancer-api-internal: tcp connection to a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 7.148747ms message: 'load-balancer-api-internal: resolved host name a999f16fcc9b54126abd7c52c7e781b4-a9b73b72adc6768e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T13:01:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-network-check-target-ip-10-0-135-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60601" uid: 9ec60707-7645-41db-bc94-f9fda573f235 spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:30:33Z" message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.098577ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 1.216321ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 1.072985ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 744.675µs message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 905.734µs message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 959.939µs message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:00:33Z" - latency: 1.264193ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:33Z" - latency: 1.866232ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:33Z" - latency: 953.964µs message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:33Z" - latency: 1.488174ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-network-check-target-ip-10-0-139-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60603" uid: 80db1ade-1efc-49ca-9525-46a336d49c4d spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:30:33Z" message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.107396ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 2.710523ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 2.167868ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 2.123712ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 2.471229ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 2.091261ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:00:33Z" - latency: 2.256329ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:33Z" - latency: 2.397827ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:33Z" - latency: 2.163339ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:33Z" - latency: 2.034453ms message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-network-check-target-ip-10-0-140-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60602" uid: 1e82f695-6c63-46d9-8943-197d57504720 spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:30:33Z" message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.006913ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 2.750207ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 1.847593ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 2.056558ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 2.145287ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 1.888341ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:00:33Z" - latency: 1.933772ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:59:33Z" - latency: 2.208328ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:58:33Z" - latency: 1.975843ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:57:33Z" - latency: 2.101054ms message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:56:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:23:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-6-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-6.ec2.internal uid: 59a2fa80-2dcc-43f6-84a9-6db14a33dd77 resourceVersion: "60607" uid: 5680c27b-a74a-4bb0-9cb9-c1cfc9b74c55 spec: sourcePod: network-check-source-869dcfcdcd-p9kpt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T12:29:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.252674ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:05:33Z" - latency: 1.848416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:05:33Z" - latency: 1.037967ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:04:33Z" - latency: 1.799742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:04:33Z" - latency: 1.308469ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:03:33Z" - latency: 1.656968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:03:33Z" - latency: 1.147947ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:02:33Z" - latency: 2.144976ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:02:33Z" - latency: 871.105µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T13:01:33Z" - latency: 2.029544ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T13:01:33Z" kind: List metadata: resourceVersion: ""