++ LOG_DIR=/var/log/contrail ++ export CONTAINER_LOG_DIR=/var/log/contrail/kubernetes-kube-manager ++ CONTAINER_LOG_DIR=/var/log/contrail/kubernetes-kube-manager ++ mkdir -p /var/log/contrail/kubernetes-kube-manager ++ log_file=/var/log/contrail/kubernetes-kube-manager/console.log ++ touch /var/log/contrail/kubernetes-kube-manager/console.log ++ chmod 600 /var/log/contrail/kubernetes-kube-manager/console.log ++ exec +++ tee -a /var/log/contrail/kubernetes-kube-manager/console.log +++ date ++ echo 'INFO: =================== Mon May 5 17:13:53 UTC 2025 ===================' INFO: =================== Mon May 5 17:13:53 UTC 2025 =================== ++ LOG_LOCAL=1 ++ source /functions.sh ++ source /contrail-functions.sh +++ get_default_ip ++++ get_default_nic ++++ get_gateway_nic_for_ip 1 ++++ command -v ip ++++ local ip=1 +++++ awk '{print $2}' +++++ grep -o 'dev.*' +++++ ip route get 1 ++++ local iface=ens3 ++++ [[ ens3 == \l\o ]] ++++ echo ens3 +++ local nic=ens3 +++ get_ip_for_nic ens3 +++ local nic=ens3 +++ get_cidr_for_nic ens3 +++ command -v ip +++ local nic=ens3 +++ cut -d / -f 1 +++ grep 'inet ' +++ ip addr show dev ens3 +++ awk '{print $2}' +++ head -n 1 ++ DEFAULT_LOCAL_IP=10.0.0.38 ++ ENCAP_PRIORITY=MPLSoUDP,MPLSoGRE,VXLAN ++ VXLAN_VN_ID_MODE=automatic ++ DPDK_UIO_DRIVER=uio_pci_generic ++ CPU_CORE_MASK=0x01 ++ SERVICE_CORE_MASK= ++ DPDK_CTRL_THREAD_MASK= ++ HUGE_PAGES= ++ HUGE_PAGES_DIR=/dev/hugepages ++ HUGE_PAGES_1GB=0 ++ HUGE_PAGES_2MB=0 ++ HUGE_PAGES_1GB_DIR= ++ HUGE_PAGES_2MB_DIR= ++ [[ 0 != 0 ]] ++ [[ 0 != 0 ]] ++ DPDK_MEM_PER_SOCKET=1024 ++ DPDK_COMMAND_ADDITIONAL_ARGS= ++ NIC_OFFLOAD_ENABLE=False ++ DPDK_ENABLE_VLAN_FWRD=False ++ DIST_SNAT_PROTO_PORT_LIST=tcp:1024,udp:1024 ++ CLOUD_ORCHESTRATOR=kubernetes ++ CLOUD_ADMIN_ROLE=admin ++ AAA_MODE=no-auth ++ AUTH_MODE=noauth ++ AUTH_PARAMS= ++ SSL_ENABLE=False ++ SSL_INSECURE=True ++ SERVER_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ SERVER_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ SERVER_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ SERVER_CA_KEYFILE=/etc/contrail/ssl/private/ca-key.pem ++ SELFSIGNED_CERTS_WITH_IPS=True ++ CONTROLLER_NODES=10.0.0.38 ++ ANALYTICS_ALARM_ENABLE=False ++ ANALYTICS_SNMP_ENABLE=False ++ ANALYTICSDB_ENABLE=False ++ ANALYTICS_NODES=10.0.0.38 ++ ANALYTICSDB_NODES=10.0.0.38 ++ ANALYTICS_SNMP_NODES=10.0.0.38 ++ ANALYTICS_API_PORT=8081 ++ ANALYTICS_API_INTROSPECT_PORT=8090 ++ ANALYTICSDB_PORT=9160 ++ ANALYTICSDB_CQL_PORT=9042 ++ TOPOLOGY_INTROSPECT_PORT=5921 ++ QUERYENGINE_INTROSPECT_PORT=8091 +++ get_server_list ANALYTICS ':8081 ' +++ local server_typ=ANALYTICS_NODES +++ local 'port_with_delim=:8081 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:8081 ' +++ '[' -n '10.0.0.38:8081 ' ']' +++ echo 10.0.0.38:8081 ++ ANALYTICS_SERVERS=10.0.0.38:8081 +++ get_server_list ANALYTICSDB ':9042 ' +++ local server_typ=ANALYTICSDB_NODES +++ local 'port_with_delim=:9042 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:9042 ' +++ '[' -n '10.0.0.38:9042 ' ']' +++ echo 10.0.0.38:9042 ++ ANALYTICSDB_CQL_SERVERS=10.0.0.38:9042 ++ ANALYTICS_API_VIP= ++ ANALYTICS_ALARM_NODES=10.0.0.38 ++ ALARMGEN_INTROSPECT_PORT=5995 ++ BGP_PORT=179 ++ BGP_AUTO_MESH=true ++ BGP_ASN=64512 ++ ENABLE_4BYTE_AS=false ++ APPLY_DEFAULTS=true ++ COLLECTOR_PORT=8086 ++ COLLECTOR_INTROSPECT_PORT=8089 ++ COLLECTOR_SYSLOG_PORT=514 ++ COLLECTOR_SFLOW_PORT=6343 ++ COLLECTOR_IPFIX_PORT=4739 ++ COLLECTOR_PROTOBUF_PORT=3333 ++ COLLECTOR_STRUCTURED_SYSLOG_PORT=3514 ++ SNMPCOLLECTOR_INTROSPECT_PORT=5920 +++ get_server_list ANALYTICS ':8086 ' +++ local server_typ=ANALYTICS_NODES +++ local 'port_with_delim=:8086 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:8086 ' +++ '[' -n '10.0.0.38:8086 ' ']' +++ echo 10.0.0.38:8086 ++ COLLECTOR_SERVERS=10.0.0.38:8086 ++ CASSANDRA_PORT=9160 ++ CASSANDRA_CQL_PORT=9042 ++ CASSANDRA_SSL_STORAGE_PORT=7011 ++ CASSANDRA_STORAGE_PORT=7010 ++ CASSANDRA_JMX_LOCAL_PORT=7200 ++ CONFIGDB_CASSANDRA_DRIVER=cql ++ CONFIG_NODES=10.0.0.38 ++ CONFIGDB_NODES=10.0.0.38 ++ CONFIG_API_PORT=8082 ++ CONFIG_API_INTROSPECT_PORT=8084 ++ CONFIG_API_ADMIN_PORT=8095 ++ CONFIGDB_PORT=9161 ++ CONFIGDB_CQL_PORT=9041 +++ get_server_list CONFIG ':8082 ' +++ local server_typ=CONFIG_NODES +++ local 'port_with_delim=:8082 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:8082 ' +++ '[' -n '10.0.0.38:8082 ' ']' +++ echo 10.0.0.38:8082 ++ CONFIG_SERVERS=10.0.0.38:8082 +++ get_server_list CONFIGDB ':9161 ' +++ local server_typ=CONFIGDB_NODES +++ local 'port_with_delim=:9161 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:9161 ' +++ '[' -n '10.0.0.38:9161 ' ']' +++ echo 10.0.0.38:9161 ++ CONFIGDB_SERVERS=10.0.0.38:9161 +++ get_server_list CONFIGDB ':9041 ' +++ local server_typ=CONFIGDB_NODES +++ local 'port_with_delim=:9041 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:9041 ' +++ '[' -n '10.0.0.38:9041 ' ']' +++ echo 10.0.0.38:9041 ++ CONFIGDB_CQL_SERVERS=10.0.0.38:9041 ++ CONFIG_API_VIP= ++ CONFIG_API_SSL_ENABLE=False ++ CONFIG_API_SERVER_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ CONFIG_API_SERVER_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ CONFIG_API_SERVER_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ CONFIG_API_WORKER_COUNT=1 ++ CONFIG_API_MAX_REQUESTS=1024 ++ ANALYTICS_API_SSL_ENABLE=False ++ ANALYTICS_API_SSL_INSECURE=True ++ ANALYTICS_API_SERVER_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ ANALYTICS_API_SERVER_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ ANALYTICS_API_SERVER_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ CASSANDRA_SSL_ENABLE=False ++ CASSANDRA_SSL_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ CASSANDRA_SSL_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ CASSANDRA_SSL_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ CASSANDRA_SSL_KEYSTORE_PASSWORD=astrophytum ++ CASSANDRA_SSL_TRUSTSTORE_PASSWORD=ornatum ++ CASSANDRA_SSL_PROTOCOL=TLS ++ CASSANDRA_SSL_ALGORITHM=SunX509 ++ CASSANDRA_SSL_CIPHER_SUITES='[TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA]' ++ CASSANDRA_CONFIG_MEMTABLE_FLUSH_WRITER=4 ++ CASSANDRA_CONFIG_CONCURRECT_COMPACTORS=4 ++ CASSANDRA_CONFIG_COMPACTION_THROUGHPUT_MB_PER_SEC=256 ++ CASSANDRA_CONFIG_CONCURRECT_READS=64 ++ CASSANDRA_CONFIG_CONCURRECT_WRITES=64 ++ CASSANDRA_CONFIG_MEMTABLE_ALLOCATION_TYPE=offheap_objects ++ CASSANDRA_REAPER_ENABLED=false ++ CASSANDRA_REAPER_JMX_KEY=reaperJmxKey ++ CASSANDRA_REAPER_JMX_AUTH_USERNAME=reaperUser ++ CASSANDRA_REAPER_JMX_AUTH_PASSWORD=reaperPass ++ CASSANDRA_REAPER_APP_PORT=8071 ++ CASSANDRA_REAPER_ADM_PORT=8072 ++ CONTROL_NODES=10.0.0.38 ++ CONTROL_INTROSPECT_PORT=8083 ++ DNS_NODES=10.0.0.38 ++ DNS_SERVER_PORT=53 ++ DNS_INTROSPECT_PORT=8092 ++ RNDC_KEY=xvysmOR8lnUQRBcunkC6vg== ++ USE_EXTERNAL_TFTP=False ++ ZOOKEEPER_NODES=10.0.0.38 ++ ZOOKEEPER_PORT=2181 ++ ZOOKEEPER_PORTS=2888:3888 +++ get_server_list ZOOKEEPER :2181, +++ local server_typ=ZOOKEEPER_NODES +++ local port_with_delim=:2181, +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+=10.0.0.38:2181, +++ '[' -n 10.0.0.38:2181, ']' +++ echo 10.0.0.38:2181 ++ ZOOKEEPER_SERVERS=10.0.0.38:2181 +++ get_server_list ZOOKEEPER ':2181 ' +++ local server_typ=ZOOKEEPER_NODES +++ local 'port_with_delim=:2181 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:2181 ' +++ '[' -n '10.0.0.38:2181 ' ']' +++ echo 10.0.0.38:2181 ++ ZOOKEEPER_SERVERS_SPACE_DELIM=10.0.0.38:2181 ++ RABBITMQ_NODES=10.0.0.38 ++ RABBITMQ_NODE_PORT=5673 +++ get_server_list RABBITMQ :5673, +++ local server_typ=RABBITMQ_NODES +++ local port_with_delim=:5673, +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+=10.0.0.38:5673, +++ '[' -n 10.0.0.38:5673, ']' +++ echo 10.0.0.38:5673 ++ RABBITMQ_SERVERS=10.0.0.38:5673 ++ RABBITMQ_SSL_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ RABBITMQ_SSL_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ RABBITMQ_SSL_CACERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ RABBITMQ_SSL_FAIL_IF_NO_PEER_CERT=true ++ RABBITMQ_VHOST=/ ++ RABBITMQ_USER=guest ++ RABBITMQ_PASSWORD=guest ++ RABBITMQ_USE_SSL=False ++ RABBITMQ_SSL_VER=tlsv1.2 ++ RABBITMQ_CLIENT_SSL_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ RABBITMQ_CLIENT_SSL_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ RABBITMQ_CLIENT_SSL_CACERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ RABBITMQ_HEARTBEAT_INTERVAL=60 ++ RABBITMQ_CLUSTER_PARTITION_HANDLING=autoheal ++ RABBITMQ_MIRRORED_QUEUE_MODE=all ++ REDIS_SERVER_PORT=6379 ++ REDIS_SERVER_PASSWORD= +++ get_server_list ANALYTICS ':6379 ' +++ local server_typ=ANALYTICS_NODES +++ local 'port_with_delim=:6379 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:6379 ' +++ '[' -n '10.0.0.38:6379 ' ']' +++ echo 10.0.0.38:6379 ++ REDIS_SERVERS=10.0.0.38:6379 ++ REDIS_LISTEN_ADDRESS= ++ REDIS_PROTECTED_MODE= ++ REDIS_SSL_ENABLE=False ++ REDIS_SSL_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ REDIS_SSL_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ REDIS_SSL_CACERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ redis_ssl_config= ++ KAFKA_NODES=10.0.0.38 ++ KAFKA_PORT=9092 +++ get_server_list KAFKA ':9092 ' +++ local server_typ=KAFKA_NODES +++ local 'port_with_delim=:9092 ' +++ local server_list= +++ IFS=, +++ read -ra server_list +++ local extended_server_list= +++ for server in '"${server_list[@]}"' ++++ echo 10.0.0.38 +++ local server_address=10.0.0.38 +++ extended_server_list+='10.0.0.38:9092 ' +++ '[' -n '10.0.0.38:9092 ' ']' +++ echo 10.0.0.38:9092 ++ KAFKA_SERVERS=10.0.0.38:9092 ++ KAFKA_SSL_ENABLE=False ++ KAFKA_SSL_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ KAFKA_SSL_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ KAFKA_SSL_CACERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ KEYSTONE_AUTH_ADMIN_TENANT=admin ++ KEYSTONE_AUTH_ADMIN_USER=admin ++ KEYSTONE_AUTH_ADMIN_PASSWORD=contrail123 ++ KEYSTONE_AUTH_PROJECT_DOMAIN_NAME=Default ++ KEYSTONE_AUTH_USER_DOMAIN_NAME=Default ++ KEYSTONE_AUTH_REGION_NAME=RegionOne ++ KEYSTONE_AUTH_URL_VERSION=/ ++ KEYSTONE_AUTH_HOST=127.0.0.1 ++ KEYSTONE_AUTH_PROTO=http ++ KEYSTONE_AUTH_ADMIN_PORT=5000 ++ KEYSTONE_AUTH_PUBLIC_PORT=5000 ++ KEYSTONE_AUTH_URL_TOKENS=/v3/auth/tokens ++ KEYSTONE_AUTH_INSECURE=True ++ KEYSTONE_AUTH_CERTFILE= ++ KEYSTONE_AUTH_KEYFILE= ++ KEYSTONE_AUTH_CA_CERTFILE= ++ KEYSTONE_AUTH_ENDPOINT_TYPE= ++ KEYSTONE_AUTH_SYNC_ON_DEMAND= ++ KEYSTONE_AUTH_INTERFACE=public ++ KUBEMANAGER_NODES=10.0.0.38 ++ KUBERNETES_CLUSTER_NAME=k8s ++ KUBERNETES_CNI_META_PLUGIN=multus ++ METADATA_PROXY_SECRET=contrail ++ BARBICAN_TENANT_NAME=service ++ BARBICAN_USER=barbican ++ BARBICAN_PASSWORD=contrail123 ++ AGENT_MODE=kernel ++ EXTERNAL_ROUTERS= ++ SUBCLUSTER= ++ VROUTER_COMPUTE_NODE_ADDRESS= ++ VROUTER_CRYPT_INTERFACE=crypt0 ++ VROUTER_DECRYPT_INTERFACE=decrypt0 ++ VROUTER_DECRYPT_KEY=15 ++ VROUTER_MODULE_OPTIONS= ++ FABRIC_SNAT_HASH_TABLE_SIZE=4096 ++ TSN_EVPN_MODE=False ++ TSN_NODES='[]' ++ PRIORITY_ID= ++ PRIORITY_BANDWIDTH= ++ PRIORITY_SCHEDULING= ++ QOS_QUEUE_ID= ++ QOS_LOGICAL_QUEUES= ++ QOS_DEF_HW_QUEUE=False ++ PRIORITY_TAGGING=True ++ SLO_DESTINATION=collector ++ '[' -n '' ']' ++ SAMPLE_DESTINATION=collector ++ FLOW_EXPORT_RATE=0 ++ WEBUI_NODES=10.0.0.38 ++ WEBUI_JOB_SERVER_PORT=3000 ++ KUE_UI_PORT=3002 ++ WEBUI_HTTP_LISTEN_PORT=8180 ++ WEBUI_HTTPS_LISTEN_PORT=8143 ++ WEBUI_SSL_KEY_FILE=/etc/contrail/webui_ssl/cs-key.pem ++ WEBUI_SSL_CERT_FILE=/etc/contrail/webui_ssl/cs-cert.pem ++ WEBUI_SSL_CIPHERS=ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:AES256-SHA ++ WEBUI_STATIC_AUTH_USER=admin ++ WEBUI_STATIC_AUTH_PASSWORD=contrail123 ++ WEBUI_STATIC_AUTH_ROLE=cloudAdmin ++ XMPP_SERVER_PORT=5269 ++ XMPP_SSL_ENABLE=False ++ XMPP_SERVER_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ XMPP_SERVER_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ XMPP_SERVER_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ LINKLOCAL_SERVICE_PORT=80 ++ LINKLOCAL_SERVICE_NAME=metadata ++ LINKLOCAL_SERVICE_IP=169.254.169.254 ++ IPFABRIC_SERVICE_PORT=8775 ++ INTROSPECT_SSL_ENABLE=False ++ INTROSPECT_SSL_INSECURE=True ++ INTROSPECT_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ INTROSPECT_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ INTROSPECT_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ INTROSPECT_LISTEN_ALL=True ++ SANDESH_SSL_ENABLE=False ++ SANDESH_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ SANDESH_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ SANDESH_SERVER_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ SANDESH_SERVER_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ SANDESH_CA_CERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ METADATA_SSL_ENABLE=false ++ METADATA_SSL_CERTFILE= ++ METADATA_SSL_KEYFILE= ++ METADATA_SSL_CA_CERTFILE= ++ METADATA_SSL_CERT_TYPE= ++ CONFIGURE_IPTABLES=false ++ FWAAS_ENABLE=False ++ CONTAINERD_NAMESPACE=k8s.io ++ TOR_AGENT_OVS_KA=10000 ++ TOR_TYPE=ovs ++ TOR_OVS_PROTOCOL=tcp ++ TORAGENT_SSL_CERTFILE=/etc/contrail/ssl/certs/server.pem ++ TORAGENT_SSL_KEYFILE=/etc/contrail/ssl/private/server-privkey.pem ++ TORAGENT_SSL_CACERTFILE=/etc/contrail/ssl/certs/ca-cert.pem ++ [[ / == \/\v\2\.\0 ]] ++ [[ kubernetes == \o\p\e\n\s\t\a\c\k ]] ++ [[ noauth == \k\e\y\s\t\o\n\e ]] ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ read -r -d '' sandesh_client_config ++ true ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ xmpp_certs_config= ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ analytics_api_ssl_opts= ++ read -r -d '' rabbitmq_config ++ true ++ read -r -d '' rabbit_config ++ true ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ kafka_ssl_config= ++ [[ -n '' ]] ++ collector_stats_config= ++ [[ -z '' ]] ++ is_enabled False ++ local val=false ++ [[ false == \t\r\u\e ]] ++ [[ false == \y\e\s ]] ++ [[ false == \e\n\a\b\l\e\d ]] ++ export TSN_AGENT_MODE= ++ TSN_AGENT_MODE= ++ [[ -n '' ]] ++ collector_stats_config= ++ [[ -z x ]] ++ RSYSLOGD_XFLOW_LISTEN_PORT=9898 + pre_start_init + wait_certs_if_ssl_enabled + is_ssl_enabled + is_enabled False + local val=false + [[ false == \t\r\u\e ]] + [[ false == \y\e\s ]] + [[ false == \e\n\a\b\l\e\d ]] + is_enabled False + local val=false + [[ false == \t\r\u\e ]] + [[ false == \y\e\s ]] + [[ false == \e\n\a\b\l\e\d ]] + is_enabled False + local val=false + [[ false == \t\r\u\e ]] + [[ false == \y\e\s ]] + [[ false == \e\n\a\b\l\e\d ]] + is_enabled False + local val=false + [[ false == \t\r\u\e ]] + [[ false == \y\e\s ]] + [[ false == \e\n\a\b\l\e\d ]] + return + wait_for_cassandra ++ cut -d , -f 1 ++ echo 10.0.0.38 + local cassandra=10.0.0.38 + (( i=1 )) + (( i<=30 )) + echo -e '\035\nquit' + nc -z 10.0.0.38 9041 + echo 'INFO: Cassandra is connected' INFO: Cassandra is connected + sleep 5 + return 0 + K8S_TOKEN_FILE=/var/run/secrets/kubernetes.io/serviceaccount/token + K8S_TOKEN=eyJhbGciOiJSUzI1NiIsImtpZCI6IlZLSkNaYXRwcXdTaWMwNjg1WExXamN4ZDRuR2EzS1dMR3oxWndCTF91N0UifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJjb250cmFpbCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJjb250cmFpbC1rdWJlbWFuYWdlciIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJjb250cmFpbC1rdWJlbWFuYWdlciIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjYyNGUwZWEzLTAzYzMtNDhlNC1hNTkzLTIxMzUwYzRmM2UyMiIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjb250cmFpbDpjb250cmFpbC1rdWJlbWFuYWdlciJ9.EDGuaSP4URKH6Ca3kKb5f_OB3JmCMGYuMzV02kY-d0jKeorglyzcOJdhjUJvY-728aWigHkBMwgGP3eAHnnW1e-l5m9If2TMV9tvEqGKEG49Z4BiEFk5bgi8URS8Uo7Ip5UtbPa2FLhZqYr5BjugOfjicQxTnT9p6bPAxgNiR7C0Kg0wHl1zYLrV87vOWcgYhc-sZxsj74TordoYnloTXWFvao5CP72eYlAJo_DADknpLJNVVgY0JQyhnEy42lZnTh4yGAkLGRwRZhfuqnPKN4yfA67zyvOVjZZWTsFqH0sVyMjZFMmBpyqCLSYNy3TDo4d4t3U-YibbIjUrzlTs2g ++ get_listen_ip_for_node KUBEMANAGER +++ find_my_ip_and_order_for_node KUBEMANAGER +++ cut -d ' ' -f 1 +++ local server_typ=KUBEMANAGER_NODES +++ find_my_ip_and_order_for_node_list 10.0.0.38 +++ local servers=10.0.0.38 +++ local server_list= +++ IFS=, +++ read -ra server_list ++++ get_local_ips ++++ tr '\n' , ++++ awk '/32 host/ { print f } {f=$2}' ++++ grep -vi host ++++ sort ++++ uniq ++++ cat /proc/net/fib_trie +++ local local_ips=,10.0.0.38,10.222.251.1,127.0.0.1,172.17.0.1,252.38.0.1,, +++ local ord=1 +++ for server in '"${server_list[@]}"' +++ local ret=0 ++++ python3 -c 'import socket; print(socket.gethostbyname('\''10.0.0.38'\''))' +++ local server_ip=10.0.0.38 +++ [[ 0 == 0 ]] +++ [[ -n 10.0.0.38 ]] +++ [[ ,10.0.0.38,10.222.251.1,127.0.0.1,172.17.0.1,252.38.0.1,, =~ ,10\.0\.0\.38, ]] +++ echo 10.0.0.38 1 +++ return ++ local ip=10.0.0.38 ++ [[ -z 10.0.0.38 ]] ++ echo 10.0.0.38 + host_ip=10.0.0.38 + [[ cql == \c\q\l ]] ++ echo 10.0.0.38:9041 ++ sed 's/,/ /g' + cassandra_server_list=10.0.0.38:9041 + mkdir -p /etc/contrail + cat ++ get_introspect_listen_ip_for_node KUBEMANAGER ++ local ip=0.0.0.0 ++ is_enabled True ++ local val=true ++ [[ true == \t\r\u\e ]] ++ echo 0.0.0.0 + [[ noauth == \k\e\y\s\t\o\n\e ]] + add_ini_params_from_env KUBERNETES /etc/contrail/contrail-kubernetes.conf + local service_name=KUBERNETES + local cfg_path=/etc/contrail/contrail-kubernetes.conf + local delim=__ ++ sort ++ grep '^KUBERNETES__.*__.*=.*$' ++ cut -d = -f 1 ++ sed 's/^KUBERNETES__//g' ++ set -o posix ++ set + local vars= + local section= + set_third_party_auth_config + [[ noauth != \k\e\y\s\t\o\n\e ]] + return + set_vnc_api_lib_ini + local tmp_file=/etc/contrail/vnc_api_lib.ini.tmp + cat + is_enabled False + local val=false + [[ false == \t\r\u\e ]] + [[ false == \y\e\s ]] + [[ false == \e\n\a\b\l\e\d ]] + [[ noauth == \k\e\y\s\t\o\n\e ]] + cat + mv -f /etc/contrail/vnc_api_lib.ini.tmp /etc/contrail/vnc_api_lib.ini + upgrade_old_logs kube-manager + local template=kube-manager ++ dirname /var/log/contrail/kubernetes-kube-manager + local old_dir=/var/log/contrail + mkdir -p /var/log/contrail/kubernetes-kube-manager + chmod 755 /var/log/contrail/kubernetes-kube-manager + mv -n '/var/log/contrail/*kube-manager.log*' /var/log/contrail/kubernetes-kube-manager/ + true + [[ -n 1999 ]] + [[ -n 1999 ]] + local owner_opts=1999:1999 + chown 1999:1999 /var/log/contrail/kubernetes-kube-manager + find /var/log/contrail/kubernetes-kube-manager -uid 0 -exec chown 1999:1999 '{}' + + run_service /usr/local/bin/contrail-kube-manager -c /etc/contrail/contrail-kubernetes.conf + [[ -n 1999 ]] + [[ -n 1999 ]] + local owner_opts=1999:1999 + mkdir -p /etc/contrail /var/lib/contrail + chown 1999:1999 /etc/contrail /var/lib/contrail + find /etc/contrail -uid 0 -exec chown 1999:1999 '{}' + + chmod 755 /etc/contrail + do_run_service /usr/local/bin/contrail-kube-manager -c /etc/contrail/contrail-kubernetes.conf + [[ -n 1999 ]] + [[ -n 1999 ]] + mkdir -p /var/crashes + chmod 777 /var/crashes ++ id -un 1999 + local user_name=contrail + export HOME=/home/contrail + HOME=/home/contrail + mkdir -p /home/contrail + chown -R 1999:1999 /home/contrail + exec setpriv --reuid 1999 --regid 1999 --clear-groups --no-new-privs /usr/local/bin/contrail-kube-manager -c /etc/contrail/contrail-kubernetes.conf /usr/local/lib/python3.6/site-packages/cfgm_common/vnc_kombu.py:10: MonkeyPatchWarning: Patching more than once will result in the union of all True parameters being patched gevent.monkey.patch_all() 05/05/2025 17:14:01.749 7fb8920eda48 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True 05/05/2025 17:14:01.989 7fb8920eda48 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_DEBUG] 05/05/2025 17:14:01.989 7fb8920eda48 [contrail-kube-manager] [INFO]: SANDESH: Logging: FILE: [None] -> [/var/log/contrail/kubernetes-kube-manager/contrail-kube-manager.log] 2025-05-05 17:14:02.41: KubeMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:02.41: KubeMonitor - Connect Kube API result 0 2025-05-05 17:14:02.55: KubeMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/api/v1 2025-05-05 17:14:02.57: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/api/v1 2025-05-05 17:14:02.58: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1 2025-05-05 17:14:02.58: PodMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/api/v1 2025-05-05 17:14:02.59: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/api/v1 2025-05-05 17:14:02.59: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/apis/networking.k8s.io/v1 2025-05-05 17:14:02.60: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/api/v1 2025-05-05 17:14:02.60: IngressMonitor - KubeMonitor init done: url=https://10.0.0.38:6443/apis/networking.k8s.io/v1 2025-05-05 17:14:02.60: VncKubernetes - vnc_connect starting 2025-05-05 17:14:02.62: VncKubernetes - vnc_connect done 2025-05-05 17:14:02.93: default-domain domain available. 2025-05-05 17:14:09.20: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:14:09.20: NamespaceMonitor - start process kube event 2025-05-05 17:14:09.20: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.20: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.20: NetworkMonitor - start process kube event 2025-05-05 17:14:09.20: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.20: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.21: PodMonitor - start process kube event 2025-05-05 17:14:09.21: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.21: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.21: ServiceMonitor - start process kube event 2025-05-05 17:14:09.21: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.21: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.21: NetworkPolicyMonitor - start process kube event 2025-05-05 17:14:09.21: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.21: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.21: EndPointMonitor - start process kube event 2025-05-05 17:14:09.21: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.21: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.21: IngressMonitor - start process kube event 2025-05-05 17:14:09.21: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-05-05 17:14:09.21: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:14:09.21: IngressMonitor - Connect Kube API result 0 2025-05-05 17:14:09.21: IngressMonitor - Start init url=https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses resource_version=None 2025-05-05 17:14:09.21: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:14:09.21: EndPointMonitor - Start init url=https://10.0.0.38:6443/api/v1/endpoints resource_version=None 2025-05-05 17:14:09.23: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:14:09.23: NetworkPolicyMonitor - Start init url=https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None 2025-05-05 17:14:09.23: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:14:09.23: ServiceMonitor - Start init url=https://10.0.0.38:6443/api/v1/services resource_version=None 2025-05-05 17:14:09.23: PodMonitor - Connect Kube API result 0 2025-05-05 17:14:09.23: PodMonitor - Start init url=https://10.0.0.38:6443/api/v1/pods resource_version=None 2025-05-05 17:14:09.24: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:14:09.24: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:14:09.24: NamespaceMonitor - Start init url=https://10.0.0.38:6443/api/v1/namespaces resource_version=None 2025-05-05 17:14:09.34: NetworkPolicyMonitor - Done init url=https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=397 2025-05-05 17:14:09.34: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.34: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:14:09.34: IngressMonitor - Done init url=https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses, resource_version=397 2025-05-05 17:14:09.34: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.35: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:14:09.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:14:09.37: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:14:09.40: NamespaceMonitor - Got ADDED Namespace None:contrail:400202f5-5065-4352-a5ed-b4130d628f61 2025-05-05 17:14:09.41: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:14:09.42: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:14:09.43: NamespaceMonitor - Got ADDED Namespace None:default:dae9059d-862b-474c-9d65-aaca219d59ce 2025-05-05 17:14:09.44: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:14:09.44: VncKubernetes - wait event (qsize=3 timeout=120) 2025-05-05 17:14:09.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:14:09.44: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:14:09.44: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:14:09.44: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:14:09.44: VncKubernetes - Process event (name=contrail event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace contrail:400202f5-5065-4352-a5ed-b4130d628f61 2025-05-05 17:14:09.46: NetworkMonitor - Start init url=https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None 2025-05-05 17:14:09.46: EndPointMonitor - Got ADDED Endpoints default:kubernetes:a022854c-2301-4d17-9583-0e22916edd2a 2025-05-05 17:14:09.47: PodMonitor - Got ADDED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:14:09.47: PodMonitor - Done init url=https://10.0.0.38:6443/api/v1/pods, resource_version=397 2025-05-05 17:14:09.47: PodMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.47: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:14:09.48: ServiceMonitor - Got ADDED Service default:kubernetes:7f4d1fc6-4ad5-464b-820c-da0833648e6b 2025-05-05 17:14:09.48: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:5f5e9098-05b5-42cf-b442-13265b38a0fb 2025-05-05 17:14:09.48: EndPointMonitor - Got ADDED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:14:09.48: EndPointMonitor - Done init url=https://10.0.0.38:6443/api/v1/endpoints, resource_version=397 2025-05-05 17:14:09.48: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.48: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:14:09.49: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:14:09.50: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:14:09.51: ServiceMonitor - Got ADDED Service kube-system:kube-dns:2c7ce3a3-2450-416a-954d-1fb2584599d6 2025-05-05 17:14:09.51: ServiceMonitor - Done init url=https://10.0.0.38:6443/api/v1/services, resource_version=397 2025-05-05 17:14:09.51: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.51: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:14:09.52: NamespaceMonitor - Got ADDED Namespace None:kube-public:a2f8f901-c79f-4170-88d3-1550c08c2589 2025-05-05 17:14:09.53: NetworkMonitor - Done init url=https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=403 2025-05-05 17:14:09.53: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.53: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'})(timeout=120) 2025-05-05 17:14:09.53: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:14:09.53: NamespaceMonitor - Got ADDED Namespace None:kube-system:200c26cd-2bf8-447e-a2c4-066a443b88c7 2025-05-05 17:14:09.53: NamespaceMonitor - Done init url=https://10.0.0.38:6443/api/v1/namespaces, resource_version=397 2025-05-05 17:14:09.53: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:14:09.53: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:14:09.54: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'}) 2025-05-05 17:14:09.54: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:14:11.93: VncKubernetes - wait event (qsize=14 timeout=120) 2025-05-05 17:14:11.93: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace default:dae9059d-862b-474c-9d65-aaca219d59ce 2025-05-05 17:14:14.52: VncKubernetes - wait event (qsize=13 timeout=120) 2025-05-05 17:14:14.53: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default) VncEndpoints - Got ADDED Endpoints default:kubernetes:a022854c-2301-4d17-9583-0e22916edd2a 2025-05-05 17:14:14.56: VncKubernetes - wait event (qsize=12 timeout=120) 2025-05-05 17:14:14.56: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=ADDED kind=Pod ns=kube-system) VncPod - Got ADDED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:14:16.05: VncKubernetes - wait event (qsize=11 timeout=120) 2025-05-05 17:14:16.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:14:16.06: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:14:16.06: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:14:16.06: VncKubernetes - wait event (qsize=10 timeout=120) 2025-05-05 17:14:16.06: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default) VncService - Got ADDED Service default:kubernetes:7f4d1fc6-4ad5-464b-820c-da0833648e6b 2025-05-05 17:14:16.06: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:14:16.06: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:14:16.06: PodMonitor - start process kube event 2025-05-05 17:14:16.06: empty line received 2025-05-05 17:14:16.06: PodMonitor - start process kube event 2025-05-05 17:14:17.31: VncKubernetes - wait event (qsize=10 timeout=120) 2025-05-05 17:14:17.31: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-node-lease:5f5e9098-05b5-42cf-b442-13265b38a0fb 2025-05-05 17:14:19.18: VncKubernetes - wait event (qsize=9 timeout=120) 2025-05-05 17:14:19.18: VncKubernetes - Process event (name=kube-dns event_type=ADDED kind=Endpoints ns=kube-system) VncEndpoints - Got ADDED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:14:19.20: VncKubernetes - wait event (qsize=8 timeout=120) 2025-05-05 17:14:19.20: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:14:19.20: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:14:19.20: VncKubernetes - wait event (qsize=7 timeout=120) 2025-05-05 17:14:19.20: VncKubernetes - Process event (name=kube-dns event_type=ADDED kind=Service ns=kube-system) VncService - Got ADDED Service kube-system:kube-dns:2c7ce3a3-2450-416a-954d-1fb2584599d6 2025-05-05 17:14:21.51: VncKubernetes - wait event (qsize=6 timeout=120) 2025-05-05 17:14:21.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:14:21.51: VncKubernetes - vnc_sync - Service start 2025-05-05 17:14:21.51: VncKubernetes - vnc_sync - Service done 2025-05-05 17:14:21.51: VncKubernetes - wait event (qsize=5 timeout=120) 2025-05-05 17:14:21.51: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-public:a2f8f901-c79f-4170-88d3-1550c08c2589 2025-05-05 17:14:23.94: VncKubernetes - wait event (qsize=4 timeout=120) 2025-05-05 17:14:23.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:14:23.94: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:14:23.94: VncKubernetes - wait event (qsize=3 timeout=120) 2025-05-05 17:14:23.94: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-system:200c26cd-2bf8-447e-a2c4-066a443b88c7 2025-05-05 17:14:25.68: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:14:25.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:14:25.68: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:14:25.68: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:14:25.68: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:14:25.68: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:14:25.77: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:15:09.58: PodMonitor - Received BOOKMARK: oldResVer=397 newResVer=412 2025-05-05 17:15:09.58: PodMonitor - start process kube event 2025-05-05 17:15:09.58: empty line received 2025-05-05 17:15:09.58: PodMonitor - start process kube event 2025-05-05 17:16:09.07: PodMonitor - Received BOOKMARK: oldResVer=412 newResVer=412 2025-05-05 17:16:09.07: PodMonitor - start process kube event 2025-05-05 17:16:09.07: empty line received 2025-05-05 17:16:09.07: PodMonitor - start process kube event 2025-05-05 17:16:09.42: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:16:09.42: IngressMonitor - start process kube event 2025-05-05 17:16:09.42: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:16:09.42: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:16:09.42: IngressMonitor - Connect Kube API result 0 2025-05-05 17:16:09.42: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:16:09.42: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:16:09.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:16:09.42: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:16:09.42: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:16:09.42: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:16:09.42: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:16:09.42: NetworkPolicyMonitor - start process kube event 2025-05-05 17:16:09.42: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:16:09.42: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:16:09.42: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:16:09.42: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:16:09.42: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:16:09.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:16:09.42: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:16:09.44: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:16:09.44: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:16:09.45: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:16:09.45: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:16:09.51: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:16:09.51: EndPointMonitor - start process kube event 2025-05-05 17:16:09.51: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:16:09.51: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:16:09.51: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:16:09.51: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:16:09.51: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:16:09.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:16:09.51: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:16:09.51: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:16:09.51: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:16:09.54: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:16:09.54: ServiceMonitor - start process kube event 2025-05-05 17:16:09.54: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:16:09.54: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:16:09.54: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:16:09.54: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:16:09.54: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:16:09.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:16:09.54: VncKubernetes - vnc_sync - Service start 2025-05-05 17:16:09.54: VncKubernetes - vnc_sync - Service done 2025-05-05 17:16:09.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:16:09.54: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:16:09.54: NetworkMonitor - start process kube event 2025-05-05 17:16:09.54: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=403 2025-05-05 17:16:09.54: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:16:09.54: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:16:09.54: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:16:09.54: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'})(timeout=120) 2025-05-05 17:16:09.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:16:09.54: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:16:09.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:16:09.54: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:16:09.54: NamespaceMonitor - start process kube event 2025-05-05 17:16:09.54: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:16:09.54: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:16:09.54: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:16:09.54: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:16:09.54: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:16:09.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:16:09.54: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:16:09.54: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:16:09.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:16:09.55: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:16:09.55: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'}) 2025-05-05 17:16:09.55: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:17:09.64: PodMonitor - Received BOOKMARK: oldResVer=412 newResVer=412 2025-05-05 17:17:09.64: PodMonitor - start process kube event 2025-05-05 17:17:09.64: empty line received 2025-05-05 17:17:09.64: PodMonitor - start process kube event 2025-05-05 17:18:09.45: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:18:09.45: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:18:09.45: NetworkPolicyMonitor - start process kube event 2025-05-05 17:18:09.45: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:18:09.45: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:18:09.45: IngressMonitor - start process kube event 2025-05-05 17:18:09.45: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:18:09.45: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:18:09.45: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:18:09.45: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.45: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:18:09.46: IngressMonitor - Connect Kube API result 0 2025-05-05 17:18:09.46: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.46: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:18:09.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:18:09.46: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:18:09.46: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:18:09.46: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:18:09.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:18:09.46: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:18:09.46: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:18:09.46: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:18:09.48: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:18:09.48: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:18:09.52: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:18:09.52: EndPointMonitor - start process kube event 2025-05-05 17:18:09.52: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:18:09.52: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:18:09.52: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:18:09.52: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.52: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:18:09.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:18:09.52: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:18:09.52: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:18:09.52: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:18:09.55: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:18:09.55: ServiceMonitor - start process kube event 2025-05-05 17:18:09.55: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:18:09.55: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:18:09.55: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:18:09.55: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.55: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:18:09.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:18:09.55: VncKubernetes - vnc_sync - Service start 2025-05-05 17:18:09.55: VncKubernetes - vnc_sync - Service done 2025-05-05 17:18:09.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:18:09.55: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:18:09.55: NetworkMonitor - start process kube event 2025-05-05 17:18:09.55: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=403 2025-05-05 17:18:09.55: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:18:09.55: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:18:09.55: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.55: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'})(timeout=120) 2025-05-05 17:18:09.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:18:09.56: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:18:09.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:18:09.56: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:18:09.56: NamespaceMonitor - start process kube event 2025-05-05 17:18:09.56: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:18:09.56: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:18:09.56: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:18:09.56: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.56: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:18:09.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:18:09.56: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:18:09.56: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:18:09.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:18:09.57: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:18:09.57: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:18:09.57: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'}) 2025-05-05 17:18:09.94: PodMonitor - Received BOOKMARK: oldResVer=412 newResVer=412 2025-05-05 17:18:09.94: PodMonitor - start process kube event 2025-05-05 17:18:09.94: PodMonitor - _schedule_vnc_sync 2025-05-05 17:18:09.94: empty line received 2025-05-05 17:18:09.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:18:09.94: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:18:09.95: PodMonitor - start process kube event 2025-05-05 17:18:09.96: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:18:09.96: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:18:22.78: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:18:22.78: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:18:22.78: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:18:22.79: PodMonitor - start process kube event 2025-05-05 17:18:22.79: empty line received 2025-05-05 17:18:22.79: PodMonitor - start process kube event 2025-05-05 17:18:22.80: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:18:22.80: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:18:22.80: PodMonitor - start process kube event 2025-05-05 17:18:22.80: empty line received 2025-05-05 17:18:22.80: PodMonitor - start process kube event 2025-05-05 17:18:22.80: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:18:22.80: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:18:22.80: EndPointMonitor - Received MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:18:22.80: EndPointMonitor - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:18:22.80: EndPointMonitor - start process kube event 2025-05-05 17:18:22.81: empty line received 2025-05-05 17:18:22.81: EndPointMonitor - start process kube event 2025-05-05 17:18:22.82: EndPointMonitor - Received MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:18:22.82: EndPointMonitor - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:18:22.82: EndPointMonitor - start process kube event 2025-05-05 17:18:22.82: empty line received 2025-05-05 17:18:22.82: EndPointMonitor - start process kube event 2025-05-05 17:18:22.86: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:18:22.86: VncKubernetes - Process event (name=kube-dns event_type=MODIFIED kind=Endpoints ns=kube-system) VncEndpoints - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:18:22.88: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:18:22.88: VncKubernetes - Process event (name=kube-dns event_type=MODIFIED kind=Endpoints ns=kube-system) VncEndpoints - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:18:23.50: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:19:09.03: EndPointMonitor - Received BOOKMARK: oldResVer=397 newResVer=761 2025-05-05 17:19:09.03: EndPointMonitor - start process kube event 2025-05-05 17:19:09.03: empty line received 2025-05-05 17:19:09.03: EndPointMonitor - start process kube event 2025-05-05 17:19:09.75: PodMonitor - Received BOOKMARK: oldResVer=412 newResVer=757 2025-05-05 17:19:09.75: PodMonitor - start process kube event 2025-05-05 17:19:09.75: empty line received 2025-05-05 17:19:09.75: PodMonitor - start process kube event 2025-05-05 17:20:00.18: PodMonitor - Received BOOKMARK: oldResVer=757 newResVer=757 2025-05-05 17:20:00.18: PodMonitor - start process kube event 2025-05-05 17:20:00.18: empty line received 2025-05-05 17:20:00.18: PodMonitor - start process kube event 2025-05-05 17:20:01.41: PodMonitor - Received BOOKMARK: oldResVer=757 newResVer=757 2025-05-05 17:20:01.41: PodMonitor - start process kube event 2025-05-05 17:20:01.41: empty line received 2025-05-05 17:20:01.41: PodMonitor - start process kube event 2025-05-05 17:20:02.24: stop iteration PodMonitor 2025-05-05 17:20:02.24: PodMonitor - start process kube event 2025-05-05 17:20:02.24: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=757 2025-05-05 17:20:02.24: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:20:02.24: PodMonitor - Connect Kube API result 0 2025-05-05 17:20:02.24: PodMonitor - _schedule_vnc_sync 2025-05-05 17:20:02.24: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '757'})(timeout=120) 2025-05-05 17:20:02.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:20:02.24: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:20:02.24: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:20:02.24: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:20:02.24: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '757'}) 2025-05-05 17:20:09.32: EndPointMonitor - Received BOOKMARK: oldResVer=761 newResVer=761 2025-05-05 17:20:09.32: EndPointMonitor - start process kube event 2025-05-05 17:20:09.32: empty line received 2025-05-05 17:20:09.32: EndPointMonitor - start process kube event 2025-05-05 17:20:09.48: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:20:09.48: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:20:09.48: IngressMonitor - start process kube event 2025-05-05 17:20:09.48: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:20:09.48: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:20:09.48: NetworkPolicyMonitor - start process kube event 2025-05-05 17:20:09.48: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:20:09.48: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:20:09.48: IngressMonitor - Connect Kube API result 0 2025-05-05 17:20:09.48: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:20:09.48: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:20:09.48: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:20:09.48: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:20:09.48: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:20:09.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:20:09.48: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:20:09.48: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:20:09.48: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:20:09.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:20:09.48: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:20:09.49: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:20:09.49: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:20:09.50: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:20:09.50: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:20:09.57: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:20:09.57: ServiceMonitor - start process kube event 2025-05-05 17:20:09.57: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:20:09.57: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:20:09.57: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:20:09.57: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:20:09.57: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:20:09.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:20:09.57: VncKubernetes - vnc_sync - Service start 2025-05-05 17:20:09.57: VncKubernetes - vnc_sync - Service done 2025-05-05 17:20:09.57: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:20:09.57: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:20:09.57: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:20:09.57: NamespaceMonitor - start process kube event 2025-05-05 17:20:09.57: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:20:09.57: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:20:09.57: NetworkMonitor - start process kube event 2025-05-05 17:20:09.57: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=403 2025-05-05 17:20:09.57: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:20:09.57: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:20:09.57: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:20:09.57: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'})(timeout=120) 2025-05-05 17:20:09.57: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:20:09.57: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:20:09.57: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:20:09.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:20:09.58: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:20:09.58: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:20:09.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:20:09.58: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:20:09.58: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:20:09.58: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:20:09.58: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:20:09.58: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:20:09.58: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'}) 2025-05-05 17:21:09.88: EndPointMonitor - Received BOOKMARK: oldResVer=761 newResVer=761 2025-05-05 17:21:09.88: EndPointMonitor - start process kube event 2025-05-05 17:21:09.88: empty line received 2025-05-05 17:21:09.88: EndPointMonitor - start process kube event 2025-05-05 17:21:17.52: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:21:17.52: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:21:17.52: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:21:17.52: PodMonitor - start process kube event 2025-05-05 17:21:17.52: empty line received 2025-05-05 17:21:17.52: PodMonitor - start process kube event 2025-05-05 17:21:17.54: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:21:17.54: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:21:17.54: PodMonitor - start process kube event 2025-05-05 17:21:17.54: empty line received 2025-05-05 17:21:17.54: PodMonitor - start process kube event 2025-05-05 17:21:17.54: EndPointMonitor - Received MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:21:17.54: EndPointMonitor - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:21:17.54: EndPointMonitor - start process kube event 2025-05-05 17:21:17.54: empty line received 2025-05-05 17:21:17.54: EndPointMonitor - start process kube event 2025-05-05 17:21:17.54: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:21:17.54: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:21:17.56: EndPointMonitor - Received MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:21:17.56: EndPointMonitor - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:21:17.56: EndPointMonitor - start process kube event 2025-05-05 17:21:17.56: empty line received 2025-05-05 17:21:17.56: EndPointMonitor - start process kube event 2025-05-05 17:21:17.59: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:21:17.59: VncKubernetes - Process event (name=kube-dns event_type=MODIFIED kind=Endpoints ns=kube-system) VncEndpoints - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:21:17.91: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:21:17.91: VncKubernetes - Process event (name=kube-dns event_type=MODIFIED kind=Endpoints ns=kube-system) VncEndpoints - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:21:18.49: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:22:03.16: PodMonitor - Received BOOKMARK: oldResVer=757 newResVer=1003 2025-05-05 17:22:03.16: PodMonitor - start process kube event 2025-05-05 17:22:03.16: empty line received 2025-05-05 17:22:03.16: PodMonitor - start process kube event 2025-05-05 17:22:09.50: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:22:09.50: IngressMonitor - start process kube event 2025-05-05 17:22:09.50: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:22:09.50: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:22:09.50: IngressMonitor - Connect Kube API result 0 2025-05-05 17:22:09.50: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:22:09.50: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:22:09.50: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:22:09.50: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:22:09.50: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:22:09.50: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:22:09.51: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:22:09.51: NetworkPolicyMonitor - start process kube event 2025-05-05 17:22:09.51: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:22:09.51: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:22:09.51: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:22:09.51: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:22:09.51: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:22:09.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:22:09.51: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:22:09.52: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:22:09.52: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:22:09.53: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:22:09.53: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:22:09.59: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:22:09.59: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:22:09.59: NamespaceMonitor - start process kube event 2025-05-05 17:22:09.59: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:22:09.59: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:22:09.59: ServiceMonitor - start process kube event 2025-05-05 17:22:09.59: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:22:09.59: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:22:09.59: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:22:09.59: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:22:09.59: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:22:09.59: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:22:09.59: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:22:09.59: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:22:09.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:22:09.59: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:22:09.59: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:22:09.59: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:22:09.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:22:09.59: VncKubernetes - vnc_sync - Service start 2025-05-05 17:22:09.59: VncKubernetes - vnc_sync - Service done 2025-05-05 17:22:09.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:22:09.59: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:22:09.59: NetworkMonitor - start process kube event 2025-05-05 17:22:09.59: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=403 2025-05-05 17:22:09.59: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:22:09.59: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:22:09.59: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:22:09.59: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'})(timeout=120) 2025-05-05 17:22:09.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:22:09.59: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:22:09.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:22:09.60: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:22:09.60: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'}) 2025-05-05 17:22:09.60: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:22:09.82: EndPointMonitor - Received BOOKMARK: oldResVer=761 newResVer=1009 2025-05-05 17:22:09.82: EndPointMonitor - start process kube event 2025-05-05 17:22:09.82: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:22:09.82: empty line received 2025-05-05 17:22:09.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:22:09.82: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:22:09.82: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:22:09.82: EndPointMonitor - start process kube event 2025-05-05 17:23:03.55: PodMonitor - Received BOOKMARK: oldResVer=1003 newResVer=1003 2025-05-05 17:23:03.55: PodMonitor - start process kube event 2025-05-05 17:23:03.55: empty line received 2025-05-05 17:23:03.55: PodMonitor - start process kube event 2025-05-05 17:23:09.26: IngressMonitor - Received BOOKMARK: oldResVer=397 newResVer=1087 2025-05-05 17:23:09.26: IngressMonitor - start process kube event 2025-05-05 17:23:09.26: empty line received 2025-05-05 17:23:09.26: IngressMonitor - start process kube event 2025-05-05 17:23:09.58: ServiceMonitor - Received BOOKMARK: oldResVer=397 newResVer=1075 2025-05-05 17:23:09.58: ServiceMonitor - start process kube event 2025-05-05 17:23:09.58: empty line received 2025-05-05 17:23:09.58: ServiceMonitor - start process kube event 2025-05-05 17:23:10.09: EndPointMonitor - Received BOOKMARK: oldResVer=1009 newResVer=1009 2025-05-05 17:23:10.09: EndPointMonitor - start process kube event 2025-05-05 17:23:10.09: empty line received 2025-05-05 17:23:10.09: EndPointMonitor - start process kube event 2025-05-05 17:23:10.18: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=397 newResVer=1059 2025-05-05 17:23:10.18: NetworkPolicyMonitor - start process kube event 2025-05-05 17:23:10.18: empty line received 2025-05-05 17:23:10.18: NetworkPolicyMonitor - start process kube event 2025-05-05 17:23:25.02: EndPointMonitor - Received BOOKMARK: oldResVer=1009 newResVer=1009 2025-05-05 17:23:25.02: EndPointMonitor - start process kube event 2025-05-05 17:23:25.02: empty line received 2025-05-05 17:23:25.02: EndPointMonitor - start process kube event 2025-05-05 17:23:26.06: stop iteration EndPointMonitor 2025-05-05 17:23:26.06: EndPointMonitor - start process kube event 2025-05-05 17:23:26.06: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1009 2025-05-05 17:23:26.06: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:23:26.06: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:23:26.06: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:23:26.06: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1009'})(timeout=120) 2025-05-05 17:23:26.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:23:26.07: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:23:26.07: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:23:26.07: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1009'}) 2025-05-05 17:24:03.10: PodMonitor - Received BOOKMARK: oldResVer=1003 newResVer=1003 2025-05-05 17:24:03.10: PodMonitor - start process kube event 2025-05-05 17:24:03.10: PodMonitor - _schedule_vnc_sync 2025-05-05 17:24:03.10: empty line received 2025-05-05 17:24:03.10: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:24:03.10: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:24:03.10: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:24:03.10: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:24:03.10: PodMonitor - start process kube event 2025-05-05 17:24:09.20: IngressMonitor - Received BOOKMARK: oldResVer=1087 newResVer=1087 2025-05-05 17:24:09.20: IngressMonitor - start process kube event 2025-05-05 17:24:09.20: empty line received 2025-05-05 17:24:09.20: IngressMonitor - start process kube event 2025-05-05 17:24:09.60: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:24:09.60: NamespaceMonitor - start process kube event 2025-05-05 17:24:09.60: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:24:09.60: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:24:09.60: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:24:09.60: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:24:09.60: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:24:09.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:24:09.61: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:24:09.61: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:24:09.61: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:24:09.61: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:24:09.61: NetworkMonitor - start process kube event 2025-05-05 17:24:09.61: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=403 2025-05-05 17:24:09.61: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:24:09.61: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:24:09.61: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:24:09.61: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'})(timeout=120) 2025-05-05 17:24:09.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:24:09.61: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:24:09.61: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:24:09.62: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:24:09.62: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '403'}) 2025-05-05 17:24:09.75: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:24:09.75: ServiceMonitor - start process kube event 2025-05-05 17:24:09.75: empty line received 2025-05-05 17:24:09.75: ServiceMonitor - start process kube event 2025-05-05 17:24:10.28: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:24:10.28: NetworkPolicyMonitor - start process kube event 2025-05-05 17:24:10.28: empty line received 2025-05-05 17:24:10.28: NetworkPolicyMonitor - start process kube event 2025-05-05 17:25:03.27: PodMonitor - Received BOOKMARK: oldResVer=1003 newResVer=1003 2025-05-05 17:25:03.27: PodMonitor - start process kube event 2025-05-05 17:25:03.27: empty line received 2025-05-05 17:25:03.27: PodMonitor - start process kube event 2025-05-05 17:25:09.54: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:25:09.54: ServiceMonitor - start process kube event 2025-05-05 17:25:09.54: empty line received 2025-05-05 17:25:09.54: ServiceMonitor - start process kube event 2025-05-05 17:25:09.88: NetworkMonitor - Received BOOKMARK: oldResVer=403 newResVer=1309 2025-05-05 17:25:09.88: NetworkMonitor - start process kube event 2025-05-05 17:25:09.88: empty line received 2025-05-05 17:25:09.88: NetworkMonitor - start process kube event 2025-05-05 17:25:10.05: IngressMonitor - Received BOOKMARK: oldResVer=1087 newResVer=1087 2025-05-05 17:25:10.05: IngressMonitor - start process kube event 2025-05-05 17:25:10.05: empty line received 2025-05-05 17:25:10.05: IngressMonitor - start process kube event 2025-05-05 17:25:10.46: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:25:10.46: NetworkPolicyMonitor - start process kube event 2025-05-05 17:25:10.46: empty line received 2025-05-05 17:25:10.46: NetworkPolicyMonitor - start process kube event 2025-05-05 17:25:26.07: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:25:26.07: EndPointMonitor - start process kube event 2025-05-05 17:25:26.07: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1009 2025-05-05 17:25:26.07: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:25:26.07: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:25:26.07: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:25:26.07: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1009'})(timeout=120) 2025-05-05 17:25:26.08: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:25:26.08: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:25:26.08: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:25:26.09: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1009'}) 2025-05-05 17:26:04.04: PodMonitor - Received BOOKMARK: oldResVer=1003 newResVer=1003 2025-05-05 17:26:04.04: PodMonitor - start process kube event 2025-05-05 17:26:04.04: empty line received 2025-05-05 17:26:04.04: PodMonitor - start process kube event 2025-05-05 17:26:09.49: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:26:09.49: ServiceMonitor - start process kube event 2025-05-05 17:26:09.49: empty line received 2025-05-05 17:26:09.49: ServiceMonitor - start process kube event 2025-05-05 17:26:09.62: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:26:09.63: NamespaceMonitor - start process kube event 2025-05-05 17:26:09.63: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:26:09.63: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:26:09.63: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:26:09.63: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:26:09.63: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:26:09.63: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:26:09.63: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:26:09.63: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:26:09.63: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:26:09.64: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:26:09.76: IngressMonitor - Received BOOKMARK: oldResVer=1087 newResVer=1087 2025-05-05 17:26:09.77: IngressMonitor - start process kube event 2025-05-05 17:26:09.77: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:26:09.77: empty line received 2025-05-05 17:26:09.77: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:26:09.77: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:26:09.77: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:26:09.77: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:26:09.77: IngressMonitor - start process kube event 2025-05-05 17:26:10.22: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:26:10.22: NetworkPolicyMonitor - start process kube event 2025-05-05 17:26:10.22: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:26:10.22: empty line received 2025-05-05 17:26:10.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:26:10.23: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:26:10.23: NetworkPolicyMonitor - start process kube event 2025-05-05 17:26:10.23: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:26:10.23: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:26:10.55: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:26:10.55: NetworkMonitor - start process kube event 2025-05-05 17:26:10.55: empty line received 2025-05-05 17:26:10.55: NetworkMonitor - start process kube event 2025-05-05 17:26:17.27: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:26:17.27: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:26:17.27: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:26:17.28: PodMonitor - start process kube event 2025-05-05 17:26:17.28: empty line received 2025-05-05 17:26:17.28: PodMonitor - start process kube event 2025-05-05 17:26:17.28: EndPointMonitor - Received MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:26:17.28: EndPointMonitor - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:26:17.28: EndPointMonitor - start process kube event 2025-05-05 17:26:17.28: empty line received 2025-05-05 17:26:17.28: EndPointMonitor - start process kube event 2025-05-05 17:26:17.29: PodMonitor - Received MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:26:17.29: PodMonitor - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:26:17.29: PodMonitor - start process kube event 2025-05-05 17:26:17.29: empty line received 2025-05-05 17:26:17.29: PodMonitor - start process kube event 2025-05-05 17:26:17.30: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:26:17.30: VncKubernetes - Process event (name=kube-dns event_type=MODIFIED kind=Endpoints ns=kube-system) VncEndpoints - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:26:17.30: EndPointMonitor - Received MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:26:17.30: EndPointMonitor - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:26:17.30: EndPointMonitor - start process kube event 2025-05-05 17:26:17.30: empty line received 2025-05-05 17:26:17.30: EndPointMonitor - start process kube event 2025-05-05 17:26:17.64: VncKubernetes - wait event (qsize=2 timeout=120) 2025-05-05 17:26:17.64: VncKubernetes - Process event (name=coredns-6f867cd986-q2xrb event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-6f867cd986-q2xrb:b2e84894-40b2-4245-b7aa-f6ca28245aa6 2025-05-05 17:26:17.70: VncKubernetes - wait event (qsize=1 timeout=120) 2025-05-05 17:26:17.70: VncKubernetes - Process event (name=kube-dns event_type=MODIFIED kind=Endpoints ns=kube-system) VncEndpoints - Got MODIFIED Endpoints kube-system:kube-dns:f433fdd0-fe4f-4db4-9041-921a4ae132ff 2025-05-05 17:26:18.21: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:26:26.44: EndPointMonitor - Received BOOKMARK: oldResVer=1009 newResVer=1426 2025-05-05 17:26:26.44: EndPointMonitor - start process kube event 2025-05-05 17:26:26.44: empty line received 2025-05-05 17:26:26.44: EndPointMonitor - start process kube event 2025-05-05 17:27:04.43: PodMonitor - Received BOOKMARK: oldResVer=1003 newResVer=1423 2025-05-05 17:27:04.43: PodMonitor - start process kube event 2025-05-05 17:27:04.43: empty line received 2025-05-05 17:27:04.43: PodMonitor - start process kube event 2025-05-05 17:27:09.53: IngressMonitor - Received BOOKMARK: oldResVer=1087 newResVer=1087 2025-05-05 17:27:09.53: IngressMonitor - start process kube event 2025-05-05 17:27:09.53: empty line received 2025-05-05 17:27:09.53: IngressMonitor - start process kube event 2025-05-05 17:27:09.86: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:27:09.86: ServiceMonitor - start process kube event 2025-05-05 17:27:09.86: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:27:09.86: empty line received 2025-05-05 17:27:09.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:27:09.86: VncKubernetes - vnc_sync - Service start 2025-05-05 17:27:09.86: VncKubernetes - vnc_sync - Service done 2025-05-05 17:27:09.86: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:27:09.86: ServiceMonitor - start process kube event 2025-05-05 17:27:10.53: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:27:10.53: NetworkPolicyMonitor - start process kube event 2025-05-05 17:27:10.53: empty line received 2025-05-05 17:27:10.53: NetworkPolicyMonitor - start process kube event 2025-05-05 17:27:11.49: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:27:11.49: NetworkMonitor - start process kube event 2025-05-05 17:27:11.49: empty line received 2025-05-05 17:27:11.49: NetworkMonitor - start process kube event 2025-05-05 17:27:18.81: IngressMonitor - Received BOOKMARK: oldResVer=1087 newResVer=1087 2025-05-05 17:27:18.81: IngressMonitor - start process kube event 2025-05-05 17:27:18.81: empty line received 2025-05-05 17:27:18.81: IngressMonitor - start process kube event 2025-05-05 17:27:20.20: stop iteration IngressMonitor 2025-05-05 17:27:20.20: IngressMonitor - start process kube event 2025-05-05 17:27:20.20: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1087 2025-05-05 17:27:20.20: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:27:20.20: IngressMonitor - Connect Kube API result 0 2025-05-05 17:27:20.20: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:27:20.20: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'})(timeout=120) 2025-05-05 17:27:20.20: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:27:20.20: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:27:20.20: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:27:20.20: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:27:20.21: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'}) 2025-05-05 17:27:26.79: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=1426 2025-05-05 17:27:26.79: EndPointMonitor - start process kube event 2025-05-05 17:27:26.79: empty line received 2025-05-05 17:27:26.79: EndPointMonitor - start process kube event 2025-05-05 17:27:49.78: PodMonitor - Received BOOKMARK: oldResVer=1423 newResVer=1423 2025-05-05 17:27:49.78: PodMonitor - start process kube event 2025-05-05 17:27:49.78: empty line received 2025-05-05 17:27:49.78: PodMonitor - start process kube event 2025-05-05 17:27:51.49: stop iteration PodMonitor 2025-05-05 17:27:51.49: PodMonitor - start process kube event 2025-05-05 17:27:51.49: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:27:51.49: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:27:51.49: PodMonitor - Connect Kube API result 0 2025-05-05 17:27:51.49: PodMonitor - _schedule_vnc_sync 2025-05-05 17:27:51.49: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:27:51.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:27:51.49: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:27:51.49: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:27:51.49: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:27:51.51: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:28:09.06: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:28:09.07: ServiceMonitor - start process kube event 2025-05-05 17:28:09.07: empty line received 2025-05-05 17:28:09.07: ServiceMonitor - start process kube event 2025-05-05 17:28:09.64: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:28:09.65: NamespaceMonitor - start process kube event 2025-05-05 17:28:09.65: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:28:09.65: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:28:09.65: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:28:09.65: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:28:09.65: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:28:09.65: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:28:09.65: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:28:09.65: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:28:09.65: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:28:09.66: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:28:11.04: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:28:11.04: NetworkMonitor - start process kube event 2025-05-05 17:28:11.04: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:28:11.04: empty line received 2025-05-05 17:28:11.04: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:28:11.04: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:28:11.04: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:28:11.04: NetworkMonitor - start process kube event 2025-05-05 17:28:11.09: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:28:11.09: NetworkPolicyMonitor - start process kube event 2025-05-05 17:28:11.09: empty line received 2025-05-05 17:28:11.09: NetworkPolicyMonitor - start process kube event 2025-05-05 17:28:26.59: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=1426 2025-05-05 17:28:26.59: EndPointMonitor - start process kube event 2025-05-05 17:28:26.59: empty line received 2025-05-05 17:28:26.59: EndPointMonitor - start process kube event 2025-05-05 17:29:09.99: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:29:09.99: ServiceMonitor - start process kube event 2025-05-05 17:29:09.99: empty line received 2025-05-05 17:29:09.99: ServiceMonitor - start process kube event 2025-05-05 17:29:10.62: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:29:10.62: NetworkPolicyMonitor - start process kube event 2025-05-05 17:29:10.62: empty line received 2025-05-05 17:29:10.62: NetworkPolicyMonitor - start process kube event 2025-05-05 17:29:11.72: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:29:11.72: NetworkMonitor - start process kube event 2025-05-05 17:29:11.72: empty line received 2025-05-05 17:29:11.72: NetworkMonitor - start process kube event 2025-05-05 17:29:20.22: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:29:20.22: IngressMonitor - start process kube event 2025-05-05 17:29:20.22: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1087 2025-05-05 17:29:20.22: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:29:20.22: IngressMonitor - Connect Kube API result 0 2025-05-05 17:29:20.22: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:29:20.22: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'})(timeout=120) 2025-05-05 17:29:20.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:29:20.22: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:29:20.22: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:29:20.22: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:29:20.24: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'}) 2025-05-05 17:29:26.38: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=1426 2025-05-05 17:29:26.38: EndPointMonitor - start process kube event 2025-05-05 17:29:26.38: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:29:26.38: empty line received 2025-05-05 17:29:26.38: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:29:26.38: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:29:26.38: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:29:26.38: EndPointMonitor - start process kube event 2025-05-05 17:29:51.51: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:29:51.51: PodMonitor - start process kube event 2025-05-05 17:29:51.51: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:29:51.51: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:29:51.51: PodMonitor - Connect Kube API result 0 2025-05-05 17:29:51.51: PodMonitor - _schedule_vnc_sync 2025-05-05 17:29:51.51: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:29:51.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:29:51.51: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:29:51.51: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:29:51.51: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:29:51.53: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:30:09.66: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:30:09.66: NamespaceMonitor - start process kube event 2025-05-05 17:30:09.66: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:30:09.66: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:30:09.66: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:30:09.67: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:30:09.67: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:30:09.67: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:30:09.67: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:30:09.67: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:30:09.67: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:30:09.68: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:30:09.98: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:30:09.98: ServiceMonitor - start process kube event 2025-05-05 17:30:09.98: empty line received 2025-05-05 17:30:09.98: ServiceMonitor - start process kube event 2025-05-05 17:30:10.76: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:30:10.76: NetworkPolicyMonitor - start process kube event 2025-05-05 17:30:10.76: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:30:10.76: empty line received 2025-05-05 17:30:10.76: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:30:10.76: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:30:10.76: NetworkPolicyMonitor - start process kube event 2025-05-05 17:30:10.76: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:30:10.76: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:30:12.38: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:30:12.38: NetworkMonitor - start process kube event 2025-05-05 17:30:12.38: empty line received 2025-05-05 17:30:12.38: NetworkMonitor - start process kube event 2025-05-05 17:30:26.08: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=1426 2025-05-05 17:30:26.08: EndPointMonitor - start process kube event 2025-05-05 17:30:26.09: empty line received 2025-05-05 17:30:26.09: EndPointMonitor - start process kube event 2025-05-05 17:30:36.20: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:30:36.20: ServiceMonitor - start process kube event 2025-05-05 17:30:36.20: empty line received 2025-05-05 17:30:36.20: ServiceMonitor - start process kube event 2025-05-05 17:30:37.27: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1075 2025-05-05 17:30:37.27: ServiceMonitor - start process kube event 2025-05-05 17:30:37.27: empty line received 2025-05-05 17:30:37.27: ServiceMonitor - start process kube event 2025-05-05 17:30:38.69: stop iteration ServiceMonitor 2025-05-05 17:30:38.69: ServiceMonitor - start process kube event 2025-05-05 17:30:38.69: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1075 2025-05-05 17:30:38.69: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:30:38.69: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:30:38.69: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:30:38.69: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1075'})(timeout=120) 2025-05-05 17:30:38.70: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:30:38.70: VncKubernetes - vnc_sync - Service start 2025-05-05 17:30:38.70: VncKubernetes - vnc_sync - Service done 2025-05-05 17:30:38.70: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:30:38.70: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1075'}) 2025-05-05 17:31:07.04: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1059 2025-05-05 17:31:07.04: NetworkPolicyMonitor - start process kube event 2025-05-05 17:31:07.04: empty line received 2025-05-05 17:31:07.04: NetworkPolicyMonitor - start process kube event 2025-05-05 17:31:08.51: stop iteration NetworkPolicyMonitor 2025-05-05 17:31:08.51: NetworkPolicyMonitor - start process kube event 2025-05-05 17:31:08.51: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1059 2025-05-05 17:31:08.51: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:31:08.51: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:31:08.51: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:31:08.51: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1059'})(timeout=120) 2025-05-05 17:31:08.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:31:08.52: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:31:08.52: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:31:08.52: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:31:08.52: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1059'}) 2025-05-05 17:31:11.74: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:31:11.74: NetworkMonitor - start process kube event 2025-05-05 17:31:11.74: empty line received 2025-05-05 17:31:11.74: NetworkMonitor - start process kube event 2025-05-05 17:31:20.24: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:31:20.24: IngressMonitor - start process kube event 2025-05-05 17:31:20.24: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1087 2025-05-05 17:31:20.24: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:31:20.24: IngressMonitor - Connect Kube API result 0 2025-05-05 17:31:20.24: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:31:20.24: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'})(timeout=120) 2025-05-05 17:31:20.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:31:20.24: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:31:20.24: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:31:20.24: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:31:20.25: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'}) 2025-05-05 17:31:27.00: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=1426 2025-05-05 17:31:27.00: EndPointMonitor - start process kube event 2025-05-05 17:31:27.00: empty line received 2025-05-05 17:31:27.00: EndPointMonitor - start process kube event 2025-05-05 17:31:51.53: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:31:51.53: PodMonitor - start process kube event 2025-05-05 17:31:51.53: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:31:51.53: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:31:51.53: PodMonitor - Connect Kube API result 0 2025-05-05 17:31:51.53: PodMonitor - _schedule_vnc_sync 2025-05-05 17:31:51.53: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:31:51.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:31:51.53: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:31:51.53: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:31:51.53: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:31:51.54: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:32:09.68: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:32:09.68: NamespaceMonitor - start process kube event 2025-05-05 17:32:09.68: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=397 2025-05-05 17:32:09.68: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:32:09.68: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:32:09.68: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:32:09.68: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'})(timeout=120) 2025-05-05 17:32:09.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:32:09.68: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:32:09.68: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:32:09.68: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:32:09.70: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '397'}) 2025-05-05 17:32:11.94: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:32:11.94: NetworkMonitor - start process kube event 2025-05-05 17:32:11.94: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:32:11.94: empty line received 2025-05-05 17:32:11.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:32:11.94: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:32:11.94: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:32:11.94: NetworkMonitor - start process kube event 2025-05-05 17:32:18.60: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=1426 2025-05-05 17:32:18.61: EndPointMonitor - start process kube event 2025-05-05 17:32:18.61: empty line received 2025-05-05 17:32:18.61: EndPointMonitor - start process kube event 2025-05-05 17:32:20.11: stop iteration EndPointMonitor 2025-05-05 17:32:20.11: EndPointMonitor - start process kube event 2025-05-05 17:32:20.11: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1426 2025-05-05 17:32:20.11: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:32:20.11: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:32:20.11: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:32:20.11: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'})(timeout=120) 2025-05-05 17:32:20.11: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:32:20.11: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:32:20.11: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:32:20.12: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'}) 2025-05-05 17:32:38.71: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:32:38.71: ServiceMonitor - start process kube event 2025-05-05 17:32:38.71: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1075 2025-05-05 17:32:38.71: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:32:38.71: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:32:38.71: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:32:38.71: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1075'})(timeout=120) 2025-05-05 17:32:38.71: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:32:38.71: VncKubernetes - vnc_sync - Service start 2025-05-05 17:32:38.71: VncKubernetes - vnc_sync - Service done 2025-05-05 17:32:38.71: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:32:38.72: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1075'}) 2025-05-05 17:33:08.25: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1059 newResVer=1895 2025-05-05 17:33:08.25: NetworkPolicyMonitor - start process kube event 2025-05-05 17:33:08.25: empty line received 2025-05-05 17:33:08.25: NetworkPolicyMonitor - start process kube event 2025-05-05 17:33:09.18: NamespaceMonitor - Received BOOKMARK: oldResVer=397 newResVer=1938 2025-05-05 17:33:09.18: NamespaceMonitor - start process kube event 2025-05-05 17:33:09.18: empty line received 2025-05-05 17:33:09.18: NamespaceMonitor - start process kube event 2025-05-05 17:33:12.45: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:33:12.45: NetworkMonitor - start process kube event 2025-05-05 17:33:12.45: empty line received 2025-05-05 17:33:12.45: NetworkMonitor - start process kube event 2025-05-05 17:33:20.26: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:33:20.26: IngressMonitor - start process kube event 2025-05-05 17:33:20.26: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1087 2025-05-05 17:33:20.26: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:33:20.26: IngressMonitor - Connect Kube API result 0 2025-05-05 17:33:20.26: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:33:20.26: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'})(timeout=120) 2025-05-05 17:33:20.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:33:20.26: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:33:20.26: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:33:20.26: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:33:20.27: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1087'}) 2025-05-05 17:33:38.57: ServiceMonitor - Received BOOKMARK: oldResVer=1075 newResVer=1929 2025-05-05 17:33:38.57: ServiceMonitor - start process kube event 2025-05-05 17:33:38.57: empty line received 2025-05-05 17:33:38.57: ServiceMonitor - start process kube event 2025-05-05 17:33:48.66: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:33:48.66: NetworkMonitor - start process kube event 2025-05-05 17:33:48.66: empty line received 2025-05-05 17:33:48.66: NetworkMonitor - start process kube event 2025-05-05 17:33:49.71: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=1309 2025-05-05 17:33:49.71: NetworkMonitor - start process kube event 2025-05-05 17:33:49.71: empty line received 2025-05-05 17:33:49.71: NetworkMonitor - start process kube event 2025-05-05 17:33:51.37: stop iteration NetworkMonitor 2025-05-05 17:33:51.37: NetworkMonitor - start process kube event 2025-05-05 17:33:51.37: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1309 2025-05-05 17:33:51.37: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:33:51.37: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:33:51.37: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:33:51.37: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1309'})(timeout=120) 2025-05-05 17:33:51.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:33:51.37: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:33:51.37: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:33:51.38: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1309'}) 2025-05-05 17:33:51.55: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:33:51.55: PodMonitor - start process kube event 2025-05-05 17:33:51.55: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:33:51.55: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:33:51.55: PodMonitor - Connect Kube API result 0 2025-05-05 17:33:51.55: PodMonitor - _schedule_vnc_sync 2025-05-05 17:33:51.55: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:33:51.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:33:51.55: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:33:51.55: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:33:51.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:33:51.55: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:34:08.52: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:34:08.52: NetworkPolicyMonitor - start process kube event 2025-05-05 17:34:08.52: empty line received 2025-05-05 17:34:08.52: NetworkPolicyMonitor - start process kube event 2025-05-05 17:34:09.22: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=1938 2025-05-05 17:34:09.22: NamespaceMonitor - start process kube event 2025-05-05 17:34:09.22: empty line received 2025-05-05 17:34:09.22: NamespaceMonitor - start process kube event 2025-05-05 17:34:20.12: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:34:20.12: EndPointMonitor - start process kube event 2025-05-05 17:34:20.12: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1426 2025-05-05 17:34:20.12: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:34:20.12: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:34:20.12: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:34:20.12: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'})(timeout=120) 2025-05-05 17:34:20.13: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:34:20.13: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:34:20.13: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:34:20.14: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'}) 2025-05-05 17:34:20.90: IngressMonitor - Received BOOKMARK: oldResVer=1087 newResVer=1954 2025-05-05 17:34:20.91: IngressMonitor - start process kube event 2025-05-05 17:34:20.91: empty line received 2025-05-05 17:34:20.91: IngressMonitor - start process kube event 2025-05-05 17:34:38.08: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:34:38.08: ServiceMonitor - start process kube event 2025-05-05 17:34:38.08: empty line received 2025-05-05 17:34:38.08: ServiceMonitor - start process kube event 2025-05-05 17:35:08.34: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:35:08.34: NetworkPolicyMonitor - start process kube event 2025-05-05 17:35:08.34: empty line received 2025-05-05 17:35:08.34: NetworkPolicyMonitor - start process kube event 2025-05-05 17:35:09.20: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=1938 2025-05-05 17:35:09.20: NamespaceMonitor - start process kube event 2025-05-05 17:35:09.20: empty line received 2025-05-05 17:35:09.20: NamespaceMonitor - start process kube event 2025-05-05 17:35:21.06: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=1954 2025-05-05 17:35:21.06: IngressMonitor - start process kube event 2025-05-05 17:35:21.06: empty line received 2025-05-05 17:35:21.06: IngressMonitor - start process kube event 2025-05-05 17:35:38.57: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:35:38.57: ServiceMonitor - start process kube event 2025-05-05 17:35:38.57: empty line received 2025-05-05 17:35:38.57: ServiceMonitor - start process kube event 2025-05-05 17:35:51.39: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:35:51.39: NetworkMonitor - start process kube event 2025-05-05 17:35:51.39: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1309 2025-05-05 17:35:51.39: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:35:51.39: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:35:51.39: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:35:51.39: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1309'})(timeout=120) 2025-05-05 17:35:51.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:35:51.39: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:35:51.39: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:35:51.40: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1309'}) 2025-05-05 17:35:51.56: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:35:51.56: PodMonitor - start process kube event 2025-05-05 17:35:51.56: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:35:51.56: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:35:51.56: PodMonitor - Connect Kube API result 0 2025-05-05 17:35:51.56: PodMonitor - _schedule_vnc_sync 2025-05-05 17:35:51.56: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:35:51.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:35:51.56: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:35:51.56: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:35:51.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:35:51.56: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:36:08.61: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:36:08.61: NetworkPolicyMonitor - start process kube event 2025-05-05 17:36:08.61: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:36:08.61: empty line received 2025-05-05 17:36:08.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:36:08.62: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:36:08.62: NetworkPolicyMonitor - start process kube event 2025-05-05 17:36:08.62: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:36:08.62: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:36:09.43: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=1938 2025-05-05 17:36:09.43: NamespaceMonitor - start process kube event 2025-05-05 17:36:09.43: empty line received 2025-05-05 17:36:09.43: NamespaceMonitor - start process kube event 2025-05-05 17:36:20.14: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:36:20.14: EndPointMonitor - start process kube event 2025-05-05 17:36:20.14: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1426 2025-05-05 17:36:20.14: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:36:20.14: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:36:20.14: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:36:20.14: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'})(timeout=120) 2025-05-05 17:36:20.14: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:36:20.14: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:36:20.14: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:36:20.16: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'}) 2025-05-05 17:36:21.13: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=1954 2025-05-05 17:36:21.13: IngressMonitor - start process kube event 2025-05-05 17:36:21.13: empty line received 2025-05-05 17:36:21.13: IngressMonitor - start process kube event 2025-05-05 17:36:38.95: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:36:38.95: ServiceMonitor - start process kube event 2025-05-05 17:36:38.96: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:36:38.96: empty line received 2025-05-05 17:36:38.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:36:38.96: VncKubernetes - vnc_sync - Service start 2025-05-05 17:36:38.96: VncKubernetes - vnc_sync - Service done 2025-05-05 17:36:38.96: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:36:38.96: ServiceMonitor - start process kube event 2025-05-05 17:36:51.46: NetworkMonitor - Received BOOKMARK: oldResVer=1309 newResVer=2187 2025-05-05 17:36:51.46: NetworkMonitor - start process kube event 2025-05-05 17:36:51.46: empty line received 2025-05-05 17:36:51.46: NetworkMonitor - start process kube event 2025-05-05 17:37:08.27: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:37:08.28: NetworkPolicyMonitor - start process kube event 2025-05-05 17:37:08.28: empty line received 2025-05-05 17:37:08.28: NetworkPolicyMonitor - start process kube event 2025-05-05 17:37:09.59: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=1938 2025-05-05 17:37:09.59: NamespaceMonitor - start process kube event 2025-05-05 17:37:09.59: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:37:09.59: empty line received 2025-05-05 17:37:09.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:37:09.59: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:37:09.59: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:37:09.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:37:09.59: NamespaceMonitor - start process kube event 2025-05-05 17:37:20.17: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=1954 2025-05-05 17:37:20.17: IngressMonitor - start process kube event 2025-05-05 17:37:20.17: empty line received 2025-05-05 17:37:20.17: IngressMonitor - start process kube event 2025-05-05 17:37:23.33: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=1938 2025-05-05 17:37:23.33: NamespaceMonitor - start process kube event 2025-05-05 17:37:23.33: empty line received 2025-05-05 17:37:23.33: NamespaceMonitor - start process kube event 2025-05-05 17:37:24.45: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=1938 2025-05-05 17:37:24.45: NamespaceMonitor - start process kube event 2025-05-05 17:37:24.46: empty line received 2025-05-05 17:37:24.46: NamespaceMonitor - start process kube event 2025-05-05 17:37:25.56: stop iteration NamespaceMonitor 2025-05-05 17:37:25.56: NamespaceMonitor - start process kube event 2025-05-05 17:37:25.56: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1938 2025-05-05 17:37:25.56: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:37:25.56: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:37:25.56: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:37:25.56: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'})(timeout=120) 2025-05-05 17:37:25.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:37:25.56: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:37:25.56: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:37:25.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:37:25.58: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'}) 2025-05-05 17:37:38.46: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:37:38.46: ServiceMonitor - start process kube event 2025-05-05 17:37:38.46: empty line received 2025-05-05 17:37:38.46: ServiceMonitor - start process kube event 2025-05-05 17:37:50.71: NetworkMonitor - Received BOOKMARK: oldResVer=2187 newResVer=2187 2025-05-05 17:37:50.71: NetworkMonitor - start process kube event 2025-05-05 17:37:50.71: empty line received 2025-05-05 17:37:50.71: NetworkMonitor - start process kube event 2025-05-05 17:37:51.57: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:37:51.57: PodMonitor - start process kube event 2025-05-05 17:37:51.57: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:37:51.57: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:37:51.57: PodMonitor - Connect Kube API result 0 2025-05-05 17:37:51.57: PodMonitor - _schedule_vnc_sync 2025-05-05 17:37:51.57: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:37:51.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:37:51.57: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:37:51.57: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:37:51.57: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:37:51.58: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:38:08.75: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:38:08.75: NetworkPolicyMonitor - start process kube event 2025-05-05 17:38:08.75: empty line received 2025-05-05 17:38:08.75: NetworkPolicyMonitor - start process kube event 2025-05-05 17:38:20.16: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:38:20.16: EndPointMonitor - start process kube event 2025-05-05 17:38:20.16: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1426 2025-05-05 17:38:20.16: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:38:20.16: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:38:20.16: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:38:20.16: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'})(timeout=120) 2025-05-05 17:38:20.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:38:20.16: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:38:20.16: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:38:20.17: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'}) 2025-05-05 17:38:20.73: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=1954 2025-05-05 17:38:20.73: IngressMonitor - start process kube event 2025-05-05 17:38:20.73: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:38:20.73: empty line received 2025-05-05 17:38:20.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:38:20.73: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:38:20.73: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:38:20.73: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:38:20.73: IngressMonitor - start process kube event 2025-05-05 17:38:38.81: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:38:38.81: ServiceMonitor - start process kube event 2025-05-05 17:38:38.81: empty line received 2025-05-05 17:38:38.81: ServiceMonitor - start process kube event 2025-05-05 17:38:51.05: NetworkMonitor - Received BOOKMARK: oldResVer=2187 newResVer=2187 2025-05-05 17:38:51.05: NetworkMonitor - start process kube event 2025-05-05 17:38:51.05: empty line received 2025-05-05 17:38:51.05: NetworkMonitor - start process kube event 2025-05-05 17:39:08.23: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:39:08.23: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:08.23: empty line received 2025-05-05 17:39:08.23: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:19.39: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:39:19.39: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:19.39: empty line received 2025-05-05 17:39:19.39: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:20.54: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=1895 2025-05-05 17:39:20.54: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:20.54: empty line received 2025-05-05 17:39:20.54: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:20.97: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=1954 2025-05-05 17:39:20.97: IngressMonitor - start process kube event 2025-05-05 17:39:20.97: empty line received 2025-05-05 17:39:20.97: IngressMonitor - start process kube event 2025-05-05 17:39:21.53: stop iteration NetworkPolicyMonitor 2025-05-05 17:39:21.53: NetworkPolicyMonitor - start process kube event 2025-05-05 17:39:21.53: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1895 2025-05-05 17:39:21.53: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:39:21.53: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:39:21.53: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:39:21.53: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1895'})(timeout=120) 2025-05-05 17:39:21.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:39:21.53: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:39:21.54: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:39:21.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:39:21.54: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1895'}) 2025-05-05 17:39:25.59: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:39:25.59: NamespaceMonitor - start process kube event 2025-05-05 17:39:25.59: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1938 2025-05-05 17:39:25.59: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:39:25.59: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:39:25.59: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:39:25.59: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'})(timeout=120) 2025-05-05 17:39:25.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:39:25.59: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:39:25.59: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:39:25.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:39:25.60: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'}) 2025-05-05 17:39:38.57: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:39:38.57: ServiceMonitor - start process kube event 2025-05-05 17:39:38.57: empty line received 2025-05-05 17:39:38.57: ServiceMonitor - start process kube event 2025-05-05 17:39:51.13: NetworkMonitor - Received BOOKMARK: oldResVer=2187 newResVer=2187 2025-05-05 17:39:51.13: NetworkMonitor - start process kube event 2025-05-05 17:39:51.13: empty line received 2025-05-05 17:39:51.13: NetworkMonitor - start process kube event 2025-05-05 17:39:51.58: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:39:51.58: PodMonitor - start process kube event 2025-05-05 17:39:51.58: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:39:51.58: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:39:51.58: PodMonitor - Connect Kube API result 0 2025-05-05 17:39:51.58: PodMonitor - _schedule_vnc_sync 2025-05-05 17:39:51.58: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:39:51.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:39:51.58: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:39:51.59: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:39:51.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:39:51.60: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:40:04.61: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=1954 2025-05-05 17:40:04.61: IngressMonitor - start process kube event 2025-05-05 17:40:04.62: empty line received 2025-05-05 17:40:04.62: IngressMonitor - start process kube event 2025-05-05 17:40:06.22: stop iteration IngressMonitor 2025-05-05 17:40:06.22: IngressMonitor - start process kube event 2025-05-05 17:40:06.22: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1954 2025-05-05 17:40:06.22: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:40:06.22: IngressMonitor - Connect Kube API result 0 2025-05-05 17:40:06.22: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:40:06.22: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1954'})(timeout=120) 2025-05-05 17:40:06.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:40:06.22: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:40:06.23: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:40:06.23: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:40:06.25: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1954'}) 2025-05-05 17:40:12.19: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:40:12.20: ServiceMonitor - start process kube event 2025-05-05 17:40:12.20: empty line received 2025-05-05 17:40:12.20: ServiceMonitor - start process kube event 2025-05-05 17:40:13.40: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=1929 2025-05-05 17:40:13.40: ServiceMonitor - start process kube event 2025-05-05 17:40:13.40: empty line received 2025-05-05 17:40:13.40: ServiceMonitor - start process kube event 2025-05-05 17:40:14.56: stop iteration ServiceMonitor 2025-05-05 17:40:14.56: ServiceMonitor - start process kube event 2025-05-05 17:40:14.56: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1929 2025-05-05 17:40:14.56: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:40:14.56: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:40:14.56: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:40:14.56: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1929'})(timeout=120) 2025-05-05 17:40:14.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:40:14.56: VncKubernetes - vnc_sync - Service start 2025-05-05 17:40:14.56: VncKubernetes - vnc_sync - Service done 2025-05-05 17:40:14.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:40:14.57: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1929'}) 2025-05-05 17:40:20.17: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:40:20.17: EndPointMonitor - start process kube event 2025-05-05 17:40:20.17: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1426 2025-05-05 17:40:20.17: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:40:20.17: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:40:20.17: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:40:20.17: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'})(timeout=120) 2025-05-05 17:40:20.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:40:20.18: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:40:20.18: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:40:20.18: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'}) 2025-05-05 17:40:51.43: NetworkMonitor - Received BOOKMARK: oldResVer=2187 newResVer=2187 2025-05-05 17:40:51.43: NetworkMonitor - start process kube event 2025-05-05 17:40:51.43: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:40:51.43: empty line received 2025-05-05 17:40:51.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:40:51.43: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:40:51.43: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:40:51.43: NetworkMonitor - start process kube event 2025-05-05 17:40:58.16: NetworkMonitor - Received BOOKMARK: oldResVer=2187 newResVer=2187 2025-05-05 17:40:58.16: NetworkMonitor - start process kube event 2025-05-05 17:40:58.16: empty line received 2025-05-05 17:40:58.16: NetworkMonitor - start process kube event 2025-05-05 17:40:59.67: stop iteration NetworkMonitor 2025-05-05 17:40:59.67: NetworkMonitor - start process kube event 2025-05-05 17:40:59.67: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2187 2025-05-05 17:40:59.67: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:40:59.67: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:40:59.67: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:40:59.67: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'})(timeout=120) 2025-05-05 17:40:59.67: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:40:59.67: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:40:59.67: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:40:59.67: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'}) 2025-05-05 17:41:21.55: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:41:21.55: NetworkPolicyMonitor - start process kube event 2025-05-05 17:41:21.55: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1895 2025-05-05 17:41:21.55: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:41:21.55: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:41:21.55: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:41:21.55: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1895'})(timeout=120) 2025-05-05 17:41:21.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:41:21.55: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:41:21.55: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:41:21.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:41:21.56: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1895'}) 2025-05-05 17:41:25.60: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:41:25.60: NamespaceMonitor - start process kube event 2025-05-05 17:41:25.60: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1938 2025-05-05 17:41:25.60: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:41:25.60: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:41:25.60: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:41:25.60: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'})(timeout=120) 2025-05-05 17:41:25.60: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:41:25.60: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:41:25.60: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:41:25.60: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:41:25.62: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'}) 2025-05-05 17:41:51.60: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:41:51.60: PodMonitor - start process kube event 2025-05-05 17:41:51.60: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1423 2025-05-05 17:41:51.60: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:41:51.60: PodMonitor - Connect Kube API result 0 2025-05-05 17:41:51.60: PodMonitor - _schedule_vnc_sync 2025-05-05 17:41:51.60: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'})(timeout=120) 2025-05-05 17:41:51.60: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:41:51.60: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:41:51.60: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:41:51.60: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:41:51.61: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1423'}) 2025-05-05 17:42:06.25: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:42:06.25: IngressMonitor - start process kube event 2025-05-05 17:42:06.25: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1954 2025-05-05 17:42:06.25: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:42:06.25: IngressMonitor - Connect Kube API result 0 2025-05-05 17:42:06.25: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:42:06.25: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1954'})(timeout=120) 2025-05-05 17:42:06.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:42:06.25: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:42:06.25: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:42:06.25: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:42:06.27: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1954'}) 2025-05-05 17:42:14.57: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:42:14.57: ServiceMonitor - start process kube event 2025-05-05 17:42:14.57: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1929 2025-05-05 17:42:14.57: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:42:14.57: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:42:14.58: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:42:14.58: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1929'})(timeout=120) 2025-05-05 17:42:14.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:42:14.58: VncKubernetes - vnc_sync - Service start 2025-05-05 17:42:14.58: VncKubernetes - vnc_sync - Service done 2025-05-05 17:42:14.58: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:42:14.59: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1929'}) 2025-05-05 17:42:20.19: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:42:20.19: EndPointMonitor - start process kube event 2025-05-05 17:42:20.19: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1426 2025-05-05 17:42:20.19: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:42:20.19: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:42:20.19: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:42:20.19: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'})(timeout=120) 2025-05-05 17:42:20.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:42:20.19: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:42:20.19: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:42:20.20: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1426'}) 2025-05-05 17:42:59.67: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:42:59.68: NetworkMonitor - start process kube event 2025-05-05 17:42:59.68: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2187 2025-05-05 17:42:59.68: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:42:59.68: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:42:59.68: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:42:59.68: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'})(timeout=120) 2025-05-05 17:42:59.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:42:59.68: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:42:59.68: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:42:59.69: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'}) 2025-05-05 17:43:20.13: EndPointMonitor - Received BOOKMARK: oldResVer=1426 newResVer=2657 2025-05-05 17:43:20.13: EndPointMonitor - start process kube event 2025-05-05 17:43:20.13: empty line received 2025-05-05 17:43:20.13: EndPointMonitor - start process kube event 2025-05-05 17:43:21.56: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:43:21.56: NetworkPolicyMonitor - start process kube event 2025-05-05 17:43:21.56: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1895 2025-05-05 17:43:21.56: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:43:21.56: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:43:21.56: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:43:21.56: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1895'})(timeout=120) 2025-05-05 17:43:21.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:43:21.57: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:43:21.57: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:43:21.57: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:43:21.58: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1895'}) 2025-05-05 17:43:25.62: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:43:25.62: NamespaceMonitor - start process kube event 2025-05-05 17:43:25.62: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1938 2025-05-05 17:43:25.62: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:43:25.62: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:43:25.62: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:43:25.62: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'})(timeout=120) 2025-05-05 17:43:25.62: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:43:25.62: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:43:25.62: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:43:25.62: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:43:25.63: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1938'}) 2025-05-05 17:43:51.12: PodMonitor - Received BOOKMARK: oldResVer=1423 newResVer=2742 2025-05-05 17:43:51.18: PodMonitor - start process kube event 2025-05-05 17:43:51.18: empty line received 2025-05-05 17:43:51.18: PodMonitor - start process kube event 2025-05-05 17:44:06.27: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:44:06.27: IngressMonitor - start process kube event 2025-05-05 17:44:06.27: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1954 2025-05-05 17:44:06.27: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:44:06.27: IngressMonitor - Connect Kube API result 0 2025-05-05 17:44:06.27: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:44:06.27: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1954'})(timeout=120) 2025-05-05 17:44:06.28: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:44:06.28: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:44:06.28: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:44:06.28: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:44:06.29: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1954'}) 2025-05-05 17:44:14.59: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:44:14.59: ServiceMonitor - start process kube event 2025-05-05 17:44:14.59: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=1929 2025-05-05 17:44:14.59: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:44:14.59: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:44:14.59: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:44:14.59: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1929'})(timeout=120) 2025-05-05 17:44:14.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:44:14.59: VncKubernetes - vnc_sync - Service start 2025-05-05 17:44:14.59: VncKubernetes - vnc_sync - Service done 2025-05-05 17:44:14.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:44:14.61: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '1929'}) 2025-05-05 17:44:20.01: EndPointMonitor - Received BOOKMARK: oldResVer=2657 newResVer=2657 2025-05-05 17:44:20.01: EndPointMonitor - start process kube event 2025-05-05 17:44:20.01: empty line received 2025-05-05 17:44:20.01: EndPointMonitor - start process kube event 2025-05-05 17:44:21.49: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=1895 newResVer=2707 2025-05-05 17:44:21.49: NetworkPolicyMonitor - start process kube event 2025-05-05 17:44:21.49: empty line received 2025-05-05 17:44:21.49: NetworkPolicyMonitor - start process kube event 2025-05-05 17:44:25.69: NamespaceMonitor - Received BOOKMARK: oldResVer=1938 newResVer=2772 2025-05-05 17:44:25.69: NamespaceMonitor - start process kube event 2025-05-05 17:44:25.69: empty line received 2025-05-05 17:44:25.69: NamespaceMonitor - start process kube event 2025-05-05 17:44:51.02: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=2742 2025-05-05 17:44:51.03: PodMonitor - start process kube event 2025-05-05 17:44:51.03: empty line received 2025-05-05 17:44:51.03: PodMonitor - start process kube event 2025-05-05 17:44:59.69: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:44:59.69: NetworkMonitor - start process kube event 2025-05-05 17:44:59.69: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2187 2025-05-05 17:44:59.69: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:44:59.69: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:44:59.69: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:44:59.69: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'})(timeout=120) 2025-05-05 17:44:59.69: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:44:59.69: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:44:59.69: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:44:59.70: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'}) 2025-05-05 17:45:06.65: IngressMonitor - Received BOOKMARK: oldResVer=1954 newResVer=2794 2025-05-05 17:45:06.65: IngressMonitor - start process kube event 2025-05-05 17:45:06.65: empty line received 2025-05-05 17:45:06.65: IngressMonitor - start process kube event 2025-05-05 17:45:14.94: ServiceMonitor - Received BOOKMARK: oldResVer=1929 newResVer=2756 2025-05-05 17:45:14.94: ServiceMonitor - start process kube event 2025-05-05 17:45:14.94: empty line received 2025-05-05 17:45:14.94: ServiceMonitor - start process kube event 2025-05-05 17:45:20.44: EndPointMonitor - Received BOOKMARK: oldResVer=2657 newResVer=2657 2025-05-05 17:45:20.44: EndPointMonitor - start process kube event 2025-05-05 17:45:20.44: empty line received 2025-05-05 17:45:20.44: EndPointMonitor - start process kube event 2025-05-05 17:45:22.21: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=2707 newResVer=2707 2025-05-05 17:45:22.21: NetworkPolicyMonitor - start process kube event 2025-05-05 17:45:22.21: empty line received 2025-05-05 17:45:22.21: NetworkPolicyMonitor - start process kube event 2025-05-05 17:45:25.60: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:45:25.60: NamespaceMonitor - start process kube event 2025-05-05 17:45:25.60: empty line received 2025-05-05 17:45:25.60: NamespaceMonitor - start process kube event 2025-05-05 17:45:51.97: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=2742 2025-05-05 17:45:51.97: PodMonitor - start process kube event 2025-05-05 17:45:51.97: PodMonitor - _schedule_vnc_sync 2025-05-05 17:45:51.97: empty line received 2025-05-05 17:45:51.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:45:51.97: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:45:51.97: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:45:51.97: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:45:51.97: PodMonitor - start process kube event 2025-05-05 17:46:06.62: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=2794 2025-05-05 17:46:06.62: IngressMonitor - start process kube event 2025-05-05 17:46:06.62: empty line received 2025-05-05 17:46:06.62: IngressMonitor - start process kube event 2025-05-05 17:46:14.37: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=2756 2025-05-05 17:46:14.37: ServiceMonitor - start process kube event 2025-05-05 17:46:14.37: empty line received 2025-05-05 17:46:14.37: ServiceMonitor - start process kube event 2025-05-05 17:46:20.14: EndPointMonitor - Received BOOKMARK: oldResVer=2657 newResVer=2657 2025-05-05 17:46:20.14: EndPointMonitor - start process kube event 2025-05-05 17:46:20.14: empty line received 2025-05-05 17:46:20.14: EndPointMonitor - start process kube event 2025-05-05 17:46:22.32: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=2707 newResVer=2707 2025-05-05 17:46:22.32: NetworkPolicyMonitor - start process kube event 2025-05-05 17:46:22.32: empty line received 2025-05-05 17:46:22.32: NetworkPolicyMonitor - start process kube event 2025-05-05 17:46:25.60: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:46:25.60: NamespaceMonitor - start process kube event 2025-05-05 17:46:25.60: empty line received 2025-05-05 17:46:25.60: NamespaceMonitor - start process kube event 2025-05-05 17:46:51.84: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=2742 2025-05-05 17:46:51.84: PodMonitor - start process kube event 2025-05-05 17:46:51.84: empty line received 2025-05-05 17:46:51.84: PodMonitor - start process kube event 2025-05-05 17:46:59.70: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:46:59.70: NetworkMonitor - start process kube event 2025-05-05 17:46:59.70: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2187 2025-05-05 17:46:59.70: NetworkMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:46:59.70: NetworkMonitor - Connect Kube API result 0 2025-05-05 17:46:59.70: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:46:59.70: NetworkMonitor - Start Watching request https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'})(timeout=120) 2025-05-05 17:46:59.70: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:46:59.70: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:46:59.70: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:46:59.72: NetworkMonitor - Watches https://10.0.0.38:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2187'}) 2025-05-05 17:47:07.03: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=2794 2025-05-05 17:47:07.03: IngressMonitor - start process kube event 2025-05-05 17:47:07.03: empty line received 2025-05-05 17:47:07.03: IngressMonitor - start process kube event 2025-05-05 17:47:14.60: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=2756 2025-05-05 17:47:14.60: ServiceMonitor - start process kube event 2025-05-05 17:47:14.60: empty line received 2025-05-05 17:47:14.60: ServiceMonitor - start process kube event 2025-05-05 17:47:20.26: EndPointMonitor - Received BOOKMARK: oldResVer=2657 newResVer=2657 2025-05-05 17:47:20.26: EndPointMonitor - start process kube event 2025-05-05 17:47:20.26: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:47:20.26: empty line received 2025-05-05 17:47:20.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:47:20.26: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:47:20.26: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:47:20.26: EndPointMonitor - start process kube event 2025-05-05 17:47:22.37: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=2707 newResVer=2707 2025-05-05 17:47:22.37: NetworkPolicyMonitor - start process kube event 2025-05-05 17:47:22.37: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:47:22.37: empty line received 2025-05-05 17:47:22.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:47:22.37: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:47:22.37: NetworkPolicyMonitor - start process kube event 2025-05-05 17:47:22.37: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:47:22.37: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:47:25.32: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:47:25.32: NamespaceMonitor - start process kube event 2025-05-05 17:47:25.32: empty line received 2025-05-05 17:47:25.32: NamespaceMonitor - start process kube event 2025-05-05 17:47:51.82: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=2742 2025-05-05 17:47:51.82: PodMonitor - start process kube event 2025-05-05 17:47:51.82: empty line received 2025-05-05 17:47:51.82: PodMonitor - start process kube event 2025-05-05 17:47:59.76: NetworkMonitor - Received BOOKMARK: oldResVer=2187 newResVer=3039 2025-05-05 17:47:59.76: NetworkMonitor - start process kube event 2025-05-05 17:47:59.76: empty line received 2025-05-05 17:47:59.76: NetworkMonitor - start process kube event 2025-05-05 17:48:04.25: EndPointMonitor - Received BOOKMARK: oldResVer=2657 newResVer=2657 2025-05-05 17:48:04.25: EndPointMonitor - start process kube event 2025-05-05 17:48:04.25: empty line received 2025-05-05 17:48:04.25: EndPointMonitor - start process kube event 2025-05-05 17:48:06.16: stop iteration EndPointMonitor 2025-05-05 17:48:06.16: EndPointMonitor - start process kube event 2025-05-05 17:48:06.16: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2657 2025-05-05 17:48:06.16: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:48:06.17: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:48:06.17: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:48:06.17: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2657'})(timeout=120) 2025-05-05 17:48:06.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:48:06.17: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:48:06.17: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:48:06.18: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2657'}) 2025-05-05 17:48:06.90: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=2794 2025-05-05 17:48:06.90: IngressMonitor - start process kube event 2025-05-05 17:48:06.90: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:48:06.90: empty line received 2025-05-05 17:48:06.90: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:48:06.90: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:48:06.90: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:48:06.90: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:48:06.90: IngressMonitor - start process kube event 2025-05-05 17:48:14.16: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=2742 2025-05-05 17:48:14.16: PodMonitor - start process kube event 2025-05-05 17:48:14.16: empty line received 2025-05-05 17:48:14.16: PodMonitor - start process kube event 2025-05-05 17:48:15.00: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=2756 2025-05-05 17:48:15.00: ServiceMonitor - start process kube event 2025-05-05 17:48:15.00: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:48:15.00: empty line received 2025-05-05 17:48:15.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:48:15.00: VncKubernetes - vnc_sync - Service start 2025-05-05 17:48:15.00: VncKubernetes - vnc_sync - Service done 2025-05-05 17:48:15.00: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:48:15.00: ServiceMonitor - start process kube event 2025-05-05 17:48:15.25: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=2742 2025-05-05 17:48:15.25: PodMonitor - start process kube event 2025-05-05 17:48:15.25: empty line received 2025-05-05 17:48:15.25: PodMonitor - start process kube event 2025-05-05 17:48:16.84: stop iteration PodMonitor 2025-05-05 17:48:16.84: PodMonitor - start process kube event 2025-05-05 17:48:16.84: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2742 2025-05-05 17:48:16.84: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:48:16.84: PodMonitor - Connect Kube API result 0 2025-05-05 17:48:16.84: PodMonitor - _schedule_vnc_sync 2025-05-05 17:48:16.84: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2742'})(timeout=120) 2025-05-05 17:48:16.84: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:48:16.84: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:48:16.84: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:48:16.84: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:48:16.85: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2742'}) 2025-05-05 17:48:22.71: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=2707 newResVer=2707 2025-05-05 17:48:22.71: NetworkPolicyMonitor - start process kube event 2025-05-05 17:48:22.71: empty line received 2025-05-05 17:48:22.71: NetworkPolicyMonitor - start process kube event 2025-05-05 17:48:25.39: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:48:25.39: NamespaceMonitor - start process kube event 2025-05-05 17:48:25.39: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:48:25.39: empty line received 2025-05-05 17:48:25.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:48:25.39: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:48:25.39: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:48:25.39: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:48:25.39: NamespaceMonitor - start process kube event 2025-05-05 17:48:59.86: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:48:59.86: NetworkMonitor - start process kube event 2025-05-05 17:48:59.86: empty line received 2025-05-05 17:48:59.86: NetworkMonitor - start process kube event 2025-05-05 17:49:07.19: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=2794 2025-05-05 17:49:07.19: IngressMonitor - start process kube event 2025-05-05 17:49:07.19: empty line received 2025-05-05 17:49:07.19: IngressMonitor - start process kube event 2025-05-05 17:49:14.18: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=2756 2025-05-05 17:49:14.18: ServiceMonitor - start process kube event 2025-05-05 17:49:14.18: empty line received 2025-05-05 17:49:14.18: ServiceMonitor - start process kube event 2025-05-05 17:49:21.54: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=2707 newResVer=2707 2025-05-05 17:49:21.54: NetworkPolicyMonitor - start process kube event 2025-05-05 17:49:21.54: empty line received 2025-05-05 17:49:21.54: NetworkPolicyMonitor - start process kube event 2025-05-05 17:49:23.19: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=2794 2025-05-05 17:49:23.19: IngressMonitor - start process kube event 2025-05-05 17:49:23.19: empty line received 2025-05-05 17:49:23.20: IngressMonitor - start process kube event 2025-05-05 17:49:23.42: stop iteration NetworkPolicyMonitor 2025-05-05 17:49:23.42: NetworkPolicyMonitor - start process kube event 2025-05-05 17:49:23.42: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2707 2025-05-05 17:49:23.42: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:49:23.42: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:49:23.42: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:49:23.42: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2707'})(timeout=120) 2025-05-05 17:49:23.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:49:23.42: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:49:23.43: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:49:23.43: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:49:23.43: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2707'}) 2025-05-05 17:49:24.22: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=2794 2025-05-05 17:49:24.22: IngressMonitor - start process kube event 2025-05-05 17:49:24.22: empty line received 2025-05-05 17:49:24.22: IngressMonitor - start process kube event 2025-05-05 17:49:25.46: stop iteration IngressMonitor 2025-05-05 17:49:25.46: IngressMonitor - start process kube event 2025-05-05 17:49:25.46: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2794 2025-05-05 17:49:25.46: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:49:25.46: IngressMonitor - Connect Kube API result 0 2025-05-05 17:49:25.46: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:49:25.46: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2794'})(timeout=120) 2025-05-05 17:49:25.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:49:25.46: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:49:25.46: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:49:25.46: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:49:25.47: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2794'}) 2025-05-05 17:49:25.98: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:49:25.98: NamespaceMonitor - start process kube event 2025-05-05 17:49:25.98: empty line received 2025-05-05 17:49:25.98: NamespaceMonitor - start process kube event 2025-05-05 17:50:00.27: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:50:00.27: NetworkMonitor - start process kube event 2025-05-05 17:50:00.27: empty line received 2025-05-05 17:50:00.27: NetworkMonitor - start process kube event 2025-05-05 17:50:06.18: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:50:06.18: EndPointMonitor - start process kube event 2025-05-05 17:50:06.18: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2657 2025-05-05 17:50:06.18: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:50:06.18: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:50:06.18: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:50:06.18: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2657'})(timeout=120) 2025-05-05 17:50:06.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:50:06.18: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:50:06.18: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:50:06.20: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2657'}) 2025-05-05 17:50:09.31: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=2756 2025-05-05 17:50:09.31: ServiceMonitor - start process kube event 2025-05-05 17:50:09.31: empty line received 2025-05-05 17:50:09.31: ServiceMonitor - start process kube event 2025-05-05 17:50:10.41: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=2756 2025-05-05 17:50:10.41: ServiceMonitor - start process kube event 2025-05-05 17:50:10.41: empty line received 2025-05-05 17:50:10.41: ServiceMonitor - start process kube event 2025-05-05 17:50:11.54: stop iteration ServiceMonitor 2025-05-05 17:50:11.54: ServiceMonitor - start process kube event 2025-05-05 17:50:11.54: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2756 2025-05-05 17:50:11.54: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:50:11.54: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:50:11.54: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:50:11.54: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2756'})(timeout=120) 2025-05-05 17:50:11.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:50:11.54: VncKubernetes - vnc_sync - Service start 2025-05-05 17:50:11.54: VncKubernetes - vnc_sync - Service done 2025-05-05 17:50:11.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:50:11.55: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2756'}) 2025-05-05 17:50:16.86: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:50:16.86: PodMonitor - start process kube event 2025-05-05 17:50:16.86: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2742 2025-05-05 17:50:16.86: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:50:16.86: PodMonitor - Connect Kube API result 0 2025-05-05 17:50:16.86: PodMonitor - _schedule_vnc_sync 2025-05-05 17:50:16.86: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2742'})(timeout=120) 2025-05-05 17:50:16.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:50:16.86: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:50:16.86: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:50:16.86: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:50:16.87: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2742'}) 2025-05-05 17:50:26.84: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:50:26.84: NamespaceMonitor - start process kube event 2025-05-05 17:50:26.84: empty line received 2025-05-05 17:50:26.84: NamespaceMonitor - start process kube event 2025-05-05 17:51:00.27: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:51:00.27: NetworkMonitor - start process kube event 2025-05-05 17:51:00.27: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:51:00.27: empty line received 2025-05-05 17:51:00.27: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:51:00.27: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:51:00.27: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:51:00.27: NetworkMonitor - start process kube event 2025-05-05 17:51:23.43: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:51:23.43: NetworkPolicyMonitor - start process kube event 2025-05-05 17:51:23.43: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2707 2025-05-05 17:51:23.43: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:51:23.43: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:51:23.43: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:51:23.43: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2707'})(timeout=120) 2025-05-05 17:51:23.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:51:23.43: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:51:23.44: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:51:23.44: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:51:23.45: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2707'}) 2025-05-05 17:51:25.47: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:51:25.47: IngressMonitor - start process kube event 2025-05-05 17:51:25.47: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2794 2025-05-05 17:51:25.47: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:51:25.47: IngressMonitor - Connect Kube API result 0 2025-05-05 17:51:25.47: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:51:25.47: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2794'})(timeout=120) 2025-05-05 17:51:25.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:51:25.47: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:51:25.47: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:51:25.47: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:51:25.48: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2794'}) 2025-05-05 17:51:26.05: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:51:26.05: NamespaceMonitor - start process kube event 2025-05-05 17:51:26.05: empty line received 2025-05-05 17:51:26.05: NamespaceMonitor - start process kube event 2025-05-05 17:51:49.08: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:51:49.08: NamespaceMonitor - start process kube event 2025-05-05 17:51:49.08: empty line received 2025-05-05 17:51:49.08: NamespaceMonitor - start process kube event 2025-05-05 17:51:50.23: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=2772 2025-05-05 17:51:50.23: NamespaceMonitor - start process kube event 2025-05-05 17:51:50.24: empty line received 2025-05-05 17:51:50.24: NamespaceMonitor - start process kube event 2025-05-05 17:51:51.19: stop iteration NamespaceMonitor 2025-05-05 17:51:51.19: NamespaceMonitor - start process kube event 2025-05-05 17:51:51.19: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2772 2025-05-05 17:51:51.19: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:51:51.19: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:51:51.19: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:51:51.19: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2772'})(timeout=120) 2025-05-05 17:51:51.20: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:51:51.20: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:51:51.20: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:51:51.20: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:51:51.21: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2772'}) 2025-05-05 17:51:59.96: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:51:59.96: NetworkMonitor - start process kube event 2025-05-05 17:51:59.96: empty line received 2025-05-05 17:51:59.96: NetworkMonitor - start process kube event 2025-05-05 17:52:06.20: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:52:06.20: EndPointMonitor - start process kube event 2025-05-05 17:52:06.20: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2657 2025-05-05 17:52:06.20: EndPointMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:52:06.20: EndPointMonitor - Connect Kube API result 0 2025-05-05 17:52:06.20: EndPointMonitor - _schedule_vnc_sync 2025-05-05 17:52:06.20: EndPointMonitor - Start Watching request https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2657'})(timeout=120) 2025-05-05 17:52:06.20: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-05-05 17:52:06.20: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-05-05 17:52:06.20: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:52:06.21: EndPointMonitor - Watches https://10.0.0.38:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2657'}) 2025-05-05 17:52:11.55: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:52:11.55: ServiceMonitor - start process kube event 2025-05-05 17:52:11.55: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2756 2025-05-05 17:52:11.55: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:52:11.55: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:52:11.55: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:52:11.55: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2756'})(timeout=120) 2025-05-05 17:52:11.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:52:11.55: VncKubernetes - vnc_sync - Service start 2025-05-05 17:52:11.55: VncKubernetes - vnc_sync - Service done 2025-05-05 17:52:11.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:52:11.57: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2756'}) 2025-05-05 17:52:16.87: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:52:16.87: PodMonitor - start process kube event 2025-05-05 17:52:16.87: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2742 2025-05-05 17:52:16.87: PodMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:52:16.88: PodMonitor - Connect Kube API result 0 2025-05-05 17:52:16.88: PodMonitor - _schedule_vnc_sync 2025-05-05 17:52:16.88: PodMonitor - Start Watching request https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2742'})(timeout=120) 2025-05-05 17:52:16.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-05-05 17:52:16.88: VncKubernetes - vnc_sync - Pod start 2025-05-05 17:52:16.88: VncKubernetes - vnc_sync - Pod done 2025-05-05 17:52:16.88: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:52:16.89: PodMonitor - Watches https://10.0.0.38:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2742'}) 2025-05-05 17:53:00.28: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:53:00.28: NetworkMonitor - start process kube event 2025-05-05 17:53:00.28: empty line received 2025-05-05 17:53:00.28: NetworkMonitor - start process kube event 2025-05-05 17:53:06.91: EndPointMonitor - Received BOOKMARK: oldResVer=2657 newResVer=3452 2025-05-05 17:53:06.91: EndPointMonitor - start process kube event 2025-05-05 17:53:06.91: empty line received 2025-05-05 17:53:06.91: EndPointMonitor - start process kube event 2025-05-05 17:53:23.45: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:53:23.47: NetworkPolicyMonitor - start process kube event 2025-05-05 17:53:23.47: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2707 2025-05-05 17:53:23.47: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:53:23.47: NetworkPolicyMonitor - Connect Kube API result 0 2025-05-05 17:53:23.47: NetworkPolicyMonitor - _schedule_vnc_sync 2025-05-05 17:53:23.47: NetworkPolicyMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2707'})(timeout=120) 2025-05-05 17:53:23.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-05-05 17:53:23.47: VncKubernetes - vnc_sync - NetworkPolicy start 2025-05-05 17:53:23.48: VncKubernetes - vnc_sync - NetworkPolicy done 2025-05-05 17:53:23.48: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:53:23.48: NetworkPolicyMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2707'}) 2025-05-05 17:53:25.48: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:53:25.48: IngressMonitor - start process kube event 2025-05-05 17:53:25.48: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2794 2025-05-05 17:53:25.48: IngressMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:53:25.48: IngressMonitor - Connect Kube API result 0 2025-05-05 17:53:25.48: IngressMonitor - _schedule_vnc_sync 2025-05-05 17:53:25.48: IngressMonitor - Start Watching request https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2794'})(timeout=120) 2025-05-05 17:53:25.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-05-05 17:53:25.48: VncKubernetes - vnc_sync - Ingress start 2025-05-05 17:53:25.48: VncKubernetes - vnc_sync - Ingress done 2025-05-05 17:53:25.48: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:53:25.49: IngressMonitor - Watches https://10.0.0.38:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2794'}) 2025-05-05 17:53:51.21: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:53:51.21: NamespaceMonitor - start process kube event 2025-05-05 17:53:51.21: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2772 2025-05-05 17:53:51.21: NamespaceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:53:51.21: NamespaceMonitor - Connect Kube API result 0 2025-05-05 17:53:51.21: NamespaceMonitor - _schedule_vnc_sync 2025-05-05 17:53:51.21: NamespaceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2772'})(timeout=120) 2025-05-05 17:53:51.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-05-05 17:53:51.22: VncKubernetes - vnc_sync - Namespace start 2025-05-05 17:53:51.22: VncKubernetes - vnc_sync - Namespace done 2025-05-05 17:53:51.22: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:53:51.23: NamespaceMonitor - Watches https://10.0.0.38:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2772'}) 2025-05-05 17:53:59.70: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:53:59.70: NetworkMonitor - start process kube event 2025-05-05 17:53:59.70: empty line received 2025-05-05 17:53:59.70: NetworkMonitor - start process kube event 2025-05-05 17:54:06.46: EndPointMonitor - Received BOOKMARK: oldResVer=3452 newResVer=3452 2025-05-05 17:54:06.46: EndPointMonitor - start process kube event 2025-05-05 17:54:06.46: empty line received 2025-05-05 17:54:06.46: EndPointMonitor - start process kube event 2025-05-05 17:54:11.57: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.38', port=6443): Read timed out. 2025-05-05 17:54:11.57: ServiceMonitor - start process kube event 2025-05-05 17:54:11.57: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=2756 2025-05-05 17:54:11.57: ServiceMonitor - Try to connect Kube API 10.0.0.38:6443 2025-05-05 17:54:11.57: ServiceMonitor - Connect Kube API result 0 2025-05-05 17:54:11.57: ServiceMonitor - _schedule_vnc_sync 2025-05-05 17:54:11.57: ServiceMonitor - Start Watching request https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2756'})(timeout=120) 2025-05-05 17:54:11.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-05-05 17:54:11.57: VncKubernetes - vnc_sync - Service start 2025-05-05 17:54:11.57: VncKubernetes - vnc_sync - Service done 2025-05-05 17:54:11.57: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:54:11.59: ServiceMonitor - Watches https://10.0.0.38:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '2756'}) 2025-05-05 17:54:16.13: PodMonitor - Received BOOKMARK: oldResVer=2742 newResVer=3567 2025-05-05 17:54:16.13: PodMonitor - start process kube event 2025-05-05 17:54:16.13: empty line received 2025-05-05 17:54:16.13: PodMonitor - start process kube event 2025-05-05 17:54:23.54: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=2707 newResVer=3518 2025-05-05 17:54:23.54: NetworkPolicyMonitor - start process kube event 2025-05-05 17:54:23.54: empty line received 2025-05-05 17:54:23.54: NetworkPolicyMonitor - start process kube event 2025-05-05 17:54:51.52: NamespaceMonitor - Received BOOKMARK: oldResVer=2772 newResVer=3603 2025-05-05 17:54:51.52: NamespaceMonitor - start process kube event 2025-05-05 17:54:51.52: empty line received 2025-05-05 17:54:51.52: NamespaceMonitor - start process kube event 2025-05-05 17:54:59.80: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:54:59.80: NetworkMonitor - start process kube event 2025-05-05 17:54:59.80: empty line received 2025-05-05 17:54:59.80: NetworkMonitor - start process kube event 2025-05-05 17:55:06.24: EndPointMonitor - Received BOOKMARK: oldResVer=3452 newResVer=3452 2025-05-05 17:55:06.24: EndPointMonitor - start process kube event 2025-05-05 17:55:06.24: empty line received 2025-05-05 17:55:06.24: EndPointMonitor - start process kube event 2025-05-05 17:55:11.08: ServiceMonitor - Received BOOKMARK: oldResVer=2756 newResVer=3585 2025-05-05 17:55:11.08: ServiceMonitor - start process kube event 2025-05-05 17:55:11.08: empty line received 2025-05-05 17:55:11.08: ServiceMonitor - start process kube event 2025-05-05 17:55:15.99: PodMonitor - Received BOOKMARK: oldResVer=3567 newResVer=3567 2025-05-05 17:55:15.99: PodMonitor - start process kube event 2025-05-05 17:55:16.00: empty line received 2025-05-05 17:55:16.00: PodMonitor - start process kube event 2025-05-05 17:55:23.47: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=3518 newResVer=3518 2025-05-05 17:55:23.47: NetworkPolicyMonitor - start process kube event 2025-05-05 17:55:23.47: empty line received 2025-05-05 17:55:23.47: NetworkPolicyMonitor - start process kube event 2025-05-05 17:55:25.26: IngressMonitor - Received BOOKMARK: oldResVer=2794 newResVer=3635 2025-05-05 17:55:25.26: IngressMonitor - start process kube event 2025-05-05 17:55:25.26: empty line received 2025-05-05 17:55:25.26: IngressMonitor - start process kube event 2025-05-05 17:55:51.38: NamespaceMonitor - Received BOOKMARK: oldResVer=3603 newResVer=3603 2025-05-05 17:55:51.38: NamespaceMonitor - start process kube event 2025-05-05 17:55:51.38: empty line received 2025-05-05 17:55:51.38: NamespaceMonitor - start process kube event 2025-05-05 17:56:00.27: NetworkMonitor - Received BOOKMARK: oldResVer=3039 newResVer=3039 2025-05-05 17:56:00.27: NetworkMonitor - start process kube event 2025-05-05 17:56:00.27: NetworkMonitor - _schedule_vnc_sync 2025-05-05 17:56:00.27: empty line received 2025-05-05 17:56:00.27: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-05-05 17:56:00.27: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-05-05 17:56:00.27: VncKubernetes - wait event (qsize=0 timeout=120) 2025-05-05 17:56:00.27: NetworkMonitor - start process kube event 2025-05-05 17:56:06.99: EndPointMonitor - Received BOOKMARK: oldResVer=3452 newResVer=3452 2025-05-05 17:56:06.99: EndPointMonitor - start process kube event