apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "11103"
    uid: 1b5b3d2b-a921-4d21-95f5-1ac9d55424d3
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "14678"
    uid: c1436672-feb4-4558-96e0-e618e340ac91
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:40:41Z"
      message: 'load-balancer-api-external: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.550547ms
      message: 'load-balancer-api-external: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:41Z"
    - latency: 6.492431ms
      message: 'load-balancer-api-external: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:40:41Z"
    - latency: 5.033632ms
      message: 'load-balancer-api-external: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:41Z"
    - latency: 7.082044ms
      message: 'load-balancer-api-external: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:39:41Z"
    - latency: 5.407288ms
      message: 'load-balancer-api-external: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:41Z"
    - latency: 9.100848ms
      message: 'load-balancer-api-external: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:38:41Z"
    - latency: 4.48695ms
      message: 'load-balancer-api-external: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:41Z"
    - latency: 7.929255ms
      message: 'load-balancer-api-external: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:37:41Z"
    - latency: 5.653902ms
      message: 'load-balancer-api-external: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:36:41Z"
    - latency: 15.458889ms
      message: 'load-balancer-api-external: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:36:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "14677"
    uid: a523e7dc-3b44-40fb-a70b-808f64ba3e6d
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:40:41Z"
      message: 'load-balancer-api-internal: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.587249ms
      message: 'load-balancer-api-internal: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:41Z"
    - latency: 6.617841ms
      message: 'load-balancer-api-internal: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:40:41Z"
    - latency: 4.967333ms
      message: 'load-balancer-api-internal: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:41Z"
    - latency: 7.050932ms
      message: 'load-balancer-api-internal: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:39:41Z"
    - latency: 5.489035ms
      message: 'load-balancer-api-internal: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:41Z"
    - latency: 9.189619ms
      message: 'load-balancer-api-internal: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:38:41Z"
    - latency: 4.437151ms
      message: 'load-balancer-api-internal: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:41Z"
    - latency: 7.979731ms
      message: 'load-balancer-api-internal: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:37:41Z"
    - latency: 5.662686ms
      message: 'load-balancer-api-internal: tcp connection to aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:36:41Z"
    - latency: 15.504783ms
      message: 'load-balancer-api-internal: resolved host name aaa68f95c40074f2fb326a8efff565e3-9a45e4cf685f85ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:36:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-network-check-target-ip-10-0-129-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "11108"
    uid: 2422927d-0637-49e1-8829-0d5c6e52876d
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-network-check-target-ip-10-0-139-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "11109"
    uid: 793d136f-43e3-495d-9bc6-38ad0a4316d5
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-network-check-target-ip-10-0-142-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "11110"
    uid: 5c79f20f-8ed6-4a45-9288-62efbec6474e
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:34:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-162.ec2.internal
      uid: 3f851a28-c859-4511-8532-f01fd6bf8f31
    resourceVersion: "14676"
    uid: 42b6d31a-7ce9-4c58-95b2-062d9978019b
  spec:
    sourcePod: network-check-source-6f8b768455-zp8tl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:40:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:40:41Z"
    - latency: 1.528256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:40:41Z"
    - latency: 964.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:39:41Z"
    - latency: 1.977786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:39:41Z"
    - latency: 866.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:38:41Z"
    - latency: 1.724381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:38:41Z"
    - latency: 828.435µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:37:41Z"
    - latency: 2.226184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:37:41Z"
    - latency: 960.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:36:41Z"
    - latency: 1.904665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:36:41Z"
kind: List
metadata:
  resourceVersion: ""