apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "9983"
    uid: 43fdfcfe-7b10-49b8-b8d4-9454488a8af2
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "13694"
    uid: 109ec07e-120b-4f3d-8ac3-36007c599f85
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:02:57Z"
      message: 'load-balancer-api-external: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.472959ms
      message: 'load-balancer-api-external: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:02:57Z"
    - latency: 6.832736ms
      message: 'load-balancer-api-external: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:02:57Z"
    - latency: 4.879376ms
      message: 'load-balancer-api-external: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:01:57Z"
    - latency: 10.481279ms
      message: 'load-balancer-api-external: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:01:57Z"
    - latency: 4.432294ms
      message: 'load-balancer-api-external: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:00:57Z"
    - latency: 9.816829ms
      message: 'load-balancer-api-external: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:00:57Z"
    - latency: 5.151008ms
      message: 'load-balancer-api-external: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:59:57Z"
    - latency: 7.340681ms
      message: 'load-balancer-api-external: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:59:57Z"
    - latency: 4.238525ms
      message: 'load-balancer-api-external: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:58:57Z"
    - latency: 9.834035ms
      message: 'load-balancer-api-external: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "13695"
    uid: 0dbed0df-c3f9-4364-854a-cfc3f8049838
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:02:57Z"
      message: 'load-balancer-api-internal: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.948858ms
      message: 'load-balancer-api-internal: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:02:57Z"
    - latency: 6.757014ms
      message: 'load-balancer-api-internal: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:02:57Z"
    - latency: 4.94777ms
      message: 'load-balancer-api-internal: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:01:57Z"
    - latency: 10.287849ms
      message: 'load-balancer-api-internal: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:01:57Z"
    - latency: 3.914152ms
      message: 'load-balancer-api-internal: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:00:57Z"
    - latency: 9.787361ms
      message: 'load-balancer-api-internal: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:00:57Z"
    - latency: 3.868083ms
      message: 'load-balancer-api-internal: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:59:57Z"
    - latency: 7.283302ms
      message: 'load-balancer-api-internal: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:59:57Z"
    - latency: 4.402548ms
      message: 'load-balancer-api-internal: tcp connection to a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:58:57Z"
    - latency: 9.7754ms
      message: 'load-balancer-api-internal: resolved host name a9ff71def06c54ce5b11f1a5774d6355-2f828556deb2b6ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-network-check-target-ip-10-0-131-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "9990"
    uid: e8d607d2-10b2-4f15-9986-7047d40845fd
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-network-check-target-ip-10-0-136-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "9989"
    uid: f009819d-7a97-4706-af1d-893115e0ecca
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-network-check-target-ip-10-0-139-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "9988"
    uid: ee41673f-4394-4de7-a933-c4ef600ee5d7
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T14:56:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-31.ec2.internal
      uid: feb5c807-a2ec-4001-b74b-743fceae1e21
    resourceVersion: "13693"
    uid: 0e685059-89de-4651-a14e-1aad80fda557
  spec:
    sourcePod: network-check-source-56d84b9f44-l9kmb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:02:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.187665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:02:57Z"
    - latency: 1.723287ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:02:57Z"
    - latency: 1.066874ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:01:57Z"
    - latency: 2.585685ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:01:57Z"
    - latency: 943.359µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:00:57Z"
    - latency: 2.023589ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:00:57Z"
    - latency: 2.208559ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:59:57Z"
    - latency: 1.997681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:59:57Z"
    - latency: 797.901µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T14:58:57Z"
    - latency: 1.802698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T14:58:57Z"
kind: List
metadata:
  resourceVersion: ""