added a docs note

Author: adwk67

docs/modules/airflow/examples/example-airflow-gitsync-https.yaml

@@ -22,7 +22,8 @@ spec:
           --rev: HEAD # <10>
           # --rev: git-sync-tag # N.B. tag must be covered by "depth" (the number of commits to clone)
           # --rev: 39ee3598bd9946a1d958a448c9f7d3774d7a8043 # N.B. commit must be covered by "depth"
-          --git-config: http.sslCAInfo:/tmp/ca-cert/ca.crt # <11>
+          # --git-config: http.sslCAInfo:/tmp/ca-cert/ca.crt # N.B. this will trigger a warning if caCertSecretName is also supplied
+        caCertSecretName: git-ca-cert # <11>
   webservers:
     ...
 ---

docs/modules/airflow/pages/usage-guide/mounting-dags.adoc

@@ -65,10 +65,12 @@ include::example$example-airflow-gitsync-https.yaml[]
     This should include two fields: `user` and `password` (which can be either a password -- which is not recommended -- or a GitHub token, as described https://github.com/kubernetes/git-sync/tree/v3.6.4#flags-which-configure-authentication[here])
 <9> A map of optional configuration settings that are listed in https://github.com/kubernetes/git-sync/tree/v4.2.1?tab=readme-ov-file#manual[this] configuration section (and the ones that follow on that link)
 <10> An example showing how to specify a target revision (the default is HEAD).
-     The revision can also be a tag or a commit, though this assumes that the target hash is contained within the number of commits specified by `depth`.
-     If a tag or commit hash is specified, then git-sync recognizes this and does not perform further cloning.
-<11> Git-sync settings can be provided inline, although some of these (`--dest`, `--root`) are specified internally in the operator and are ignored if provided by the user.
-     Git-config settings can also be specified, although a warning is logged if `safe.directory` is specified as this is defined internally, and should not be defined by the user.
+    The revision can also be a tag or a commit, though this assumes that the target hash is contained within the number of commits specified by `depth`.
+    If a tag or commit hash is specified, then git-sync recognizes this and does not perform further cloning.
+    Git-sync settings can be provided inline, although some of these (`--dest`, `--root`) are specified internally in the operator and are ignored if provided by the user.
+    Git-config settings can also be specified, although a warning is logged if `safe.directory` is specified as this is defined internally, and should not be defined by the user.
+<11> An optional secret used for holding CA certificates that will be used to verify the git server's TLS certificate by passing it to the git config option `http.sslCAInfo` passed with the gitsync command.
+    The secret must have a key named `ca.crt` whose value is the PEM-encoded certificate bundle.
 
 .git-sync usage example: ssh
 [source,yaml]