apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "24105"
    uid: 09e5abbb-b39d-4827-8062-039172626409
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:34:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.08093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:34:46Z"
    - latency: 933.134µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:33:46Z"
    - latency: 1.006741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:32:46Z"
    - latency: 1.05295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:31:46Z"
    - latency: 1.304579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:30:46Z"
    - latency: 1.296043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:29:46Z"
    - latency: 1.163688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:28:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "28372"
    uid: bc34e7b8-9d64-44f1-816e-e79a5362a500
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:33:46Z"
      message: 'load-balancer-api-external: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.235114ms
      message: 'load-balancer-api-external: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:39:46Z"
    - latency: 6.8419ms
      message: 'load-balancer-api-external: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:39:46Z"
    - latency: 4.480594ms
      message: 'load-balancer-api-external: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:38:46Z"
    - latency: 7.473341ms
      message: 'load-balancer-api-external: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:38:46Z"
    - latency: 5.004566ms
      message: 'load-balancer-api-external: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:37:46Z"
    - latency: 7.048296ms
      message: 'load-balancer-api-external: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:37:46Z"
    - latency: 5.110083ms
      message: 'load-balancer-api-external: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:36:46Z"
    - latency: 7.332904ms
      message: 'load-balancer-api-external: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:36:46Z"
    - latency: 4.431445ms
      message: 'load-balancer-api-external: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:35:46Z"
    - latency: 6.133634ms
      message: 'load-balancer-api-external: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:35:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "28373"
    uid: 2a8a1092-8372-47d4-ba61-7ad21b03600d
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:33:46Z"
      message: 'load-balancer-api-internal: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.117492ms
      message: 'load-balancer-api-internal: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:39:46Z"
    - latency: 6.795711ms
      message: 'load-balancer-api-internal: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:39:46Z"
    - latency: 5.046824ms
      message: 'load-balancer-api-internal: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:38:46Z"
    - latency: 7.398346ms
      message: 'load-balancer-api-internal: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:38:46Z"
    - latency: 5.017082ms
      message: 'load-balancer-api-internal: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:37:46Z"
    - latency: 6.960468ms
      message: 'load-balancer-api-internal: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:37:46Z"
    - latency: 5.113983ms
      message: 'load-balancer-api-internal: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:36:46Z"
    - latency: 7.268833ms
      message: 'load-balancer-api-internal: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:36:46Z"
    - latency: 4.471065ms
      message: 'load-balancer-api-internal: tcp connection to ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:35:46Z"
    - latency: 5.98103ms
      message: 'load-balancer-api-internal: resolved host name ac11e2aabfc04416dbd930e38405b0f7-ecdb24c42bd02987.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:35:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-network-check-target-ip-10-0-128-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "24102"
    uid: d29e3f61-5ba4-4d8c-96b3-046ff6570191
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:34:46Z"
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.604405ms
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:34:46Z"
    - latency: 1.384158ms
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:33:46Z"
    - latency: 977.736µs
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:32:46Z"
    - latency: 1.010596ms
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:31:46Z"
    - latency: 1.565537ms
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:30:46Z"
    - latency: 1.769135ms
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:29:46Z"
    - latency: 1.286244ms
      message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:28:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-network-check-target-ip-10-0-132-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "24104"
    uid: cd86f773-f865-4dab-aac2-0cd8f3092f7d
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:34:46Z"
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332664ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:34:46Z"
    - latency: 2.291833ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:33:46Z"
    - latency: 2.141023ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:32:46Z"
    - latency: 1.972789ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:31:46Z"
    - latency: 2.281295ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:30:46Z"
    - latency: 2.087537ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:29:46Z"
    - latency: 2.493138ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:28:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-network-check-target-ip-10-0-138-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "24103"
    uid: 631be49b-3870-44b3-bf3c-59622741bdbe
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:34:46Z"
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.411733ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:34:46Z"
    - latency: 2.307935ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:33:46Z"
    - latency: 2.231474ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:32:46Z"
    - latency: 2.529034ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:31:46Z"
    - latency: 2.266849ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:30:46Z"
    - latency: 2.984866ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:29:46Z"
    - latency: 2.893818ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:28:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T02:27:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-216.ec2.internal
      uid: 429ac907-1a96-4ec3-86e1-f7ff4a6c269f
    resourceVersion: "28371"
    uid: 718b11f1-0f4a-403d-9842-72495db9a376
  spec:
    sourcePod: network-check-source-dbd9cf844-xp6fs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T02:33:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.109µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:39:46Z"
    - latency: 2.122402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:39:46Z"
    - latency: 987.934µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:38:46Z"
    - latency: 2.209148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:38:46Z"
    - latency: 1.085055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:37:46Z"
    - latency: 1.989714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:37:46Z"
    - latency: 859.53µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:36:46Z"
    - latency: 1.992531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:36:46Z"
    - latency: 1.109982ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T02:35:46Z"
    - latency: 1.498616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T02:35:46Z"
kind: List
metadata:
  resourceVersion: ""