In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

 I deployed Debezium according to this link:
https://debezium.io/documentation/reference/3.0/operations/kubernetes.html

I'm having a problem. I need to be in the debezium-connect-cluster-connect pod to get the connector status. I created a service of type NodePort, but I'm failing to get the connector status.

I checked the Debezium configuration and found that the following settings might be limiting:
rest.advertised.host.name = 10.233.111.78
rest.advertised.port = 8083

I want to change rest.advertised.host.name to 10.168.2.187 (the IP address of the k8s node) and rest.advertised.port to 32003 (the node port). 

I tried changing the configuration in the image, but it didn't work.

What Debezium connector do you use and what version?

3.0.8.Final

What is the connector configuration?

apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnect
metadata:
  name: debezium-connect-cluster
  namespace: qifu-develop
  annotations:
    strimzi.io/use-connector-resources: "true"
spec:
  version: 3.2.0
  image: harbor.qifu.com/qifu-develop/debezium-connect:3.0.8.Final_bug_fix
  replicas: 1
  bootstrapServers: debezium-cluster-kafka-bootstrap:9092
  config:
    config.providers: secrets
    config.providers.secrets.class: io.strimzi.kafka.KubernetesSecretConfigProvider
    group.id: connect-cluster
    offset.storage.topic: connect-offsets
    config.storage.topic: connect-configs
    status.storage.topic: connect-status
    config.storage.replication.factor: -1
    offset.storage.replication.factor: -1
    status.storage.replication.factor: -1
    REST_HOST_NAME: 10.168.2.187
    ADVERTISED_HOST_NAME: 10.168.2.187
    ADVERTISED_HOST_PORT: 32003

What behavior do you expect?

Debezium connector configuration file:

rest.advertised.host.name = 10.168.2.187
rest.advertised.port = 32003

What behavior do you see?

Debezium connector configuration file:

rest.advertised.host.name=10.233.111.78
rest.advertised.port=8083

Do you see the same behaviour using the latest released Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

yes