apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "69416" uid: 7ce20f7d-cf77-476d-abc4-3afa2fd08f78 spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T01:22:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178638ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:04:54Z" - latency: 1.03532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 885.571µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 1.231126ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 1.144525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 936.488µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 1.125119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:58:54Z" - latency: 1.23718ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:57:54Z" - latency: 856.95µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:56:54Z" - latency: 917.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:55:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "68334" uid: cb4e4021-be29-475b-acf8-775486cf1e58 spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T01:21:54Z" message: 'load-balancer-api-external: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.057598ms message: 'load-balancer-api-external: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 7.7303ms message: 'load-balancer-api-external: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:03:54Z" - latency: 4.738131ms message: 'load-balancer-api-external: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 7.583723ms message: 'load-balancer-api-external: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:02:54Z" - latency: 4.500682ms message: 'load-balancer-api-external: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 10.16926ms message: 'load-balancer-api-external: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:01:54Z" - latency: 3.612314ms message: 'load-balancer-api-external: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 6.688713ms message: 'load-balancer-api-external: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:00:54Z" - latency: 3.586413ms message: 'load-balancer-api-external: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 15.203932ms message: 'load-balancer-api-external: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T01:59:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "68335" uid: 96bfc547-f286-4d5c-8bfb-a953742b4aa7 spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T01:21:54Z" message: 'load-balancer-api-internal: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.109515ms message: 'load-balancer-api-internal: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 7.775158ms message: 'load-balancer-api-internal: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:03:54Z" - latency: 4.784805ms message: 'load-balancer-api-internal: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 7.470738ms message: 'load-balancer-api-internal: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:02:54Z" - latency: 4.533958ms message: 'load-balancer-api-internal: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 9.994474ms message: 'load-balancer-api-internal: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:01:54Z" - latency: 3.087053ms message: 'load-balancer-api-internal: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 6.658292ms message: 'load-balancer-api-internal: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T02:00:54Z" - latency: 4.160376ms message: 'load-balancer-api-internal: tcp connection to afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 15.261218ms message: 'load-balancer-api-internal: resolved host name afb12a0484ffd4fa4b6735fba06baacd-d9bb2d9a2f2c5b96.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T01:59:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-128-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "69414" uid: 854dfa41-82e3-4653-bcb1-74ce62e343cc spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T01:22:54Z" message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.936381ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:04:54Z" - latency: 1.998163ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 1.906064ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 2.027585ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 1.926464ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 1.851762ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 2.06564ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:58:54Z" - latency: 2.05875ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:57:54Z" - latency: 2.142163ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:56:54Z" - latency: 1.983426ms message: 'network-check-target-ip-10-0-128-44: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:55:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-134-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "69413" uid: 8ee77dc0-2b2e-4816-a774-fc62f5428ee2 spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T01:22:54Z" message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028972ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:04:54Z" - latency: 1.164952ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 880.233µs message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 1.436479ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 1.539382ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 1.234918ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 1.586913ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:58:54Z" - latency: 1.1883ms message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:57:54Z" - latency: 938.722µs message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:56:54Z" - latency: 890.133µs message: 'network-check-target-ip-10-0-134-254: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:55:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-ip-10-0-136-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "69415" uid: c9a66505-c9b0-43cf-87f2-e10c87f9b0b7 spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T01:22:54Z" message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.340085ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:04:54Z" - latency: 2.459823ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 1.978535ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 2.195184ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 2.392761ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 2.157023ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 2.161081ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:58:54Z" - latency: 2.203234ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:57:54Z" - latency: 2.399529ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:56:54Z" - latency: 2.319886ms message: 'network-check-target-ip-10-0-136-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:55:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T01:15:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-254-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-254.ec2.internal uid: 786c3972-2a79-4257-851e-c1a9d7cebbed resourceVersion: "68333" uid: cc2a3467-bcc7-4ea7-be14-b8dd3716e7aa spec: sourcePod: network-check-source-7bc5b6bf85-5zw5c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T01:21:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.481586ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:03:54Z" - latency: 1.861767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T02:03:54Z" - latency: 972.088µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:02:54Z" - latency: 1.820078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T02:02:54Z" - latency: 966.154µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:01:54Z" - latency: 1.883552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T02:01:54Z" - latency: 1.052337ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T02:00:54Z" - latency: 1.758038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T02:00:54Z" - latency: 836.168µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T01:59:54Z" - latency: 1.910592ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T01:59:54Z" kind: List metadata: resourceVersion: ""