apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "10649"
    uid: ecd40934-9dff-437e-90aa-a315e9e5430a
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "14394"
    uid: a26e9822-fcac-49bb-ad3a-d00e77bf648e
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T08:12:05Z"
      message: 'load-balancer-api-external: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.14952ms
      message: 'load-balancer-api-external: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:12:05Z"
    - latency: 9.303813ms
      message: 'load-balancer-api-external: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:12:05Z"
    - latency: 4.897173ms
      message: 'load-balancer-api-external: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:11:05Z"
    - latency: 10.471404ms
      message: 'load-balancer-api-external: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:11:05Z"
    - latency: 5.240521ms
      message: 'load-balancer-api-external: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:10:05Z"
    - latency: 8.997743ms
      message: 'load-balancer-api-external: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:10:05Z"
    - latency: 5.222214ms
      message: 'load-balancer-api-external: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:09:05Z"
    - latency: 16.696545ms
      message: 'load-balancer-api-external: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:09:05Z"
    - latency: 5.092574ms
      message: 'load-balancer-api-external: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:08:05Z"
    - latency: 7.664989ms
      message: 'load-balancer-api-external: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "14393"
    uid: 4490a011-1de7-4cd4-a680-0e60e188c195
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T08:12:05Z"
      message: 'load-balancer-api-internal: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.119014ms
      message: 'load-balancer-api-internal: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:12:05Z"
    - latency: 9.198071ms
      message: 'load-balancer-api-internal: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:12:05Z"
    - latency: 5.108419ms
      message: 'load-balancer-api-internal: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:11:05Z"
    - latency: 10.498521ms
      message: 'load-balancer-api-internal: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:11:05Z"
    - latency: 5.268934ms
      message: 'load-balancer-api-internal: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:10:05Z"
    - latency: 8.913937ms
      message: 'load-balancer-api-internal: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:10:05Z"
    - latency: 4.996481ms
      message: 'load-balancer-api-internal: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:09:05Z"
    - latency: 16.648889ms
      message: 'load-balancer-api-internal: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:09:05Z"
    - latency: 4.978543ms
      message: 'load-balancer-api-internal: tcp connection to aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:08:05Z"
    - latency: 7.685626ms
      message: 'load-balancer-api-internal: resolved host name aba8193b5700d428c8c5a2bcca2cc128-160027bf2060b1d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-ip-10-0-129-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "10647"
    uid: 1bfe2061-23d9-4141-ba24-9724a7ad5888
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-ip-10-0-133-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "10648"
    uid: afe3dd5b-afe8-4766-9770-245f898bc904
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-ip-10-0-138-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "10645"
    uid: 07e6d451-6acd-4617-83f3-6ea40c8d7560
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T08:06:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-63.ec2.internal
      uid: 1691aa72-4677-4f95-a56b-b3f04456d6de
    resourceVersion: "14391"
    uid: 5552d804-15af-4925-b2b4-c4cd85c86b14
  spec:
    sourcePod: network-check-source-869dcfcdcd-9v2qk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T08:12:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.077595ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:12:05Z"
    - latency: 2.088293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:12:05Z"
    - latency: 960.279µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:11:05Z"
    - latency: 2.03136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:11:05Z"
    - latency: 977.22µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:10:05Z"
    - latency: 1.670051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:10:05Z"
    - latency: 1.20583ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:09:05Z"
    - latency: 1.881417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:09:05Z"
    - latency: 1.068446ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T08:08:05Z"
    - latency: 1.64597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T08:08:05Z"
kind: List
metadata:
  resourceVersion: ""