Skip to main content
DevOps

Return to Answer

added 3 characters in body
Source Link
simbo1905
simbo1905
  • 1.2k
  • 5
  • 14

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently namesnamed spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t an “image puller” intountil you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently names spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t an “image puller” into you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently named spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t an “image puller” until you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.

added 2 characters in body
Source Link
simbo1905
simbo1905
  • 1.2k
  • 5
  • 14

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently names spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t in image pulleran “image puller” into you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently names spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t in image puller into you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently names spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t an “image puller” into you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.

Source Link
simbo1905
simbo1905
  • 1.2k
  • 5
  • 14

Okay the answer to this is that you can set spec.serviceAccountName on the dc and the secrets are mounted.

Annoyingly the same does not hold true for BuildConfig objects. They have an inconsistently names spec.serviceAccount. Setting that doesn’t mount any secrets associated with the sa. It also means your build isn’t in image puller into you explicitly set that up. So this configuration option appears pretty useless as at openshift 3.11.