apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "22762"
    uid: da92e8b7-3b09-455f-b2a8-4903a836ba44
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:27:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.216751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:27:06Z"
    - latency: 893.305µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 824.884µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 847.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 895.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 845.43µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 1.047013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:21:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "21621"
    uid: 5a3f6bad-1862-4ed4-a46c-7a97d5cbfe08
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:26:06Z"
      message: 'load-balancer-api-external: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.56545ms
      message: 'load-balancer-api-external: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 6.710732ms
      message: 'load-balancer-api-external: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 3.269267ms
      message: 'load-balancer-api-external: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 8.901402ms
      message: 'load-balancer-api-external: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 5.254967ms
      message: 'load-balancer-api-external: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 6.799188ms
      message: 'load-balancer-api-external: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 6.150997ms
      message: 'load-balancer-api-external: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 6.867258ms
      message: 'load-balancer-api-external: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 3.968608ms
      message: 'load-balancer-api-external: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 7.296079ms
      message: 'load-balancer-api-external: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:22:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "21620"
    uid: 3f203471-b1c8-47d3-9b9f-18ad21e336aa
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:26:06Z"
      message: 'load-balancer-api-internal: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.532323ms
      message: 'load-balancer-api-internal: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 6.606285ms
      message: 'load-balancer-api-internal: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 3.258308ms
      message: 'load-balancer-api-internal: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 8.809742ms
      message: 'load-balancer-api-internal: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 5.215296ms
      message: 'load-balancer-api-internal: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 6.721031ms
      message: 'load-balancer-api-internal: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 6.078987ms
      message: 'load-balancer-api-internal: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 6.91199ms
      message: 'load-balancer-api-internal: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 3.998125ms
      message: 'load-balancer-api-internal: tcp connection to a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 7.177144ms
      message: 'load-balancer-api-internal: resolved host name a1a0d19e4c02c4b9ea2400f9fb2ea1dc-766b52854ce6ed20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:22:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-network-check-target-ip-10-0-132-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "22761"
    uid: 87fc8323-f145-4996-b889-bf4c0353a6e8
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:27:06Z"
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372043ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:27:06Z"
    - latency: 1.986525ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 2.000707ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 1.982023ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 2.058154ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 2.183243ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 1.913994ms
      message: 'network-check-target-ip-10-0-132-168: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:21:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-network-check-target-ip-10-0-136-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "22760"
    uid: dda7d434-0995-42b7-b471-d841ac0e1620
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:27:06Z"
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.269267ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:27:06Z"
    - latency: 2.133756ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 2.23603ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 2.08097ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 2.073889ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 1.934615ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 2.178403ms
      message: 'network-check-target-ip-10-0-136-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:21:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-network-check-target-ip-10-0-138-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "22759"
    uid: c11acd67-9e06-4f2f-a87f-aa0a894e8640
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:27:06Z"
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.012µs
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:27:06Z"
    - latency: 968.808µs
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 1.114508ms
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 1.351554ms
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 919.738µs
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 844.425µs
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 1.636698ms
      message: 'network-check-target-ip-10-0-138-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:21:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T04:20:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-12.ec2.internal
      uid: 7bd4034c-c2cb-41b4-ad78-161651d5a441
    resourceVersion: "21619"
    uid: 0bf652d4-8e9e-4cc4-b195-bce084032d21
  spec:
    sourcePod: network-check-source-7cbc45fddc-fjdtl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T04:26:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.209408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 1.716622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:26:06Z"
    - latency: 870.821µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 1.709845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:25:06Z"
    - latency: 883.233µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 1.916789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:24:06Z"
    - latency: 793.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 2.029992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:23:06Z"
    - latency: 867.755µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T04:22:06Z"
    - latency: 1.729789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T04:22:06Z"
kind: List
metadata:
  resourceVersion: ""