@@ -666,11 +666,143 @@ Optional |onprem| Resource Settings
666
666
cause issues with the backup service. Excessive heaps can cause
667
667
unpredictable results in |onprem|.
668
668
669
+ .. opsmgrkube:: spec.backup.s3OpLogStores.irsaEnabled
670
+
671
+ *Type*: boolean
672
+
673
+ Flag that enables using |aws| :aws:`IAM roles for service accounts </eks/latest/userguide/iam-roles-for-service-accounts>`
674
+ in |aws| :aws:`EKS </eks/latest/userguide/what-is-eks>` to configure
675
+ an S3 oplog store. The default is ``False``. If you aren't using
676
+ |aws| EKS, this flag has no effect. When set to ``False``, using |aws|
677
+ IAM roles for service accounts in EKS to configure an S3 oplog store
678
+ is disabled. To learn more, see
679
+ :aws:`IAM roles for service accounts in EKS </eks/latest/userguide/iam-roles-for-service-accounts>`.
680
+
681
+
682
+ .. opsmgrkube:: spec.backup.s3OpLogStores.name
683
+
684
+ *Type*: string
685
+
686
+ *Required to store the oplog using an S3 store.*
687
+
688
+ Name of the |s3| oplog store.
689
+
690
+ .. opsmgrkube:: spec.backup.s3OpLogStores.mongodbResourceRef.name
691
+
692
+ *Type*: string
693
+
694
+ Name of the MongoDB database resource that you create to store
695
+ metadata for the |s3| oplog store. You must deploy this database
696
+ resource in the same namespace as the |onprem| resource.
697
+
698
+ .. note::
699
+
700
+ Omit this setting to use the application database to store
701
+ metadata for the |s3| oplog store.
702
+
703
+ If you omit this setting, you must also omit the
704
+ :opsmgrkube:`spec.backup.s3OpLogStores.mongodbUserRef.name` setting.
705
+ The |k8s-op-short| handles ``SCRAM`` user authentication
706
+ internally.
707
+
708
+ If you enable ``SCRAM`` authentication on this database, you must:
709
+
710
+ - Create a MongoDB user resource to connect |onprem| to the
711
+ database.
712
+ - Specify the
713
+ :opsmgrkube:`~spec.backup.s3OpLogStores.mongodbUserRef.name` of the
714
+ user in the |onprem| resource definition.
715
+
716
+ .. opsmgrkube:: spec.backup.s3OpLogStores.mongodbUserRef.name
717
+
718
+ *Type*: string
719
+
720
+ *Required if you created a MongoDB database resource to store
721
+ |s3| oplog metadata and SCRAM is enabled on this database.*
722
+
723
+ Name of the MongoDB user resource used to connect to the metadata
724
+ database of the |s3| oplog store. Deploy this user resource in the
725
+ same namespace as the |onprem| resource and with the
726
+ :manual:`readWriteAnyDatabase </reference/built-in-roles/#readWriteAnyDatabase>` and
727
+ :manual:`dbAdminAnyDatabase </reference/built-in-roles/#dbAdminAnyDatabase>` roles.
728
+
729
+ .. important::
730
+
731
+ Once specified, do not edit the name of the |s3| metadata oplog
732
+ store username.
733
+
734
+ .. opsmgrkube:: spec.backup.s3OpLogStores.s3SecretRef.name
735
+
736
+ *Type*: string
737
+
738
+ *Required to store the oplog using an S3 store.*
739
+
740
+ Name of the secret that contains the ``accessKey`` and
741
+ ``secretKey`` fields. The :opsmgr:`backup daemon service
742
+ </current/core/system-overview/#backup-daemon-service>` uses
743
+ the values of these fields as credentials to access your
744
+ |aws| |s3| or |s3|-compatible bucket. The |s3| oplog store
745
+ can't be configured if the secret is missing either key.
746
+
747
+ .. opsmgrkube:: spec.backup.s3OpLogStores.pathStyleAccessEnabled
748
+
749
+ *Type*: boolean
750
+
751
+ Indicates the style of the bucket endpoint URL.
752
+
753
+ .. list-table::
754
+ :widths: 30 30 30
755
+ :header-rows: 1
756
+
757
+ * - Value
758
+ - Description
759
+ - Example
760
+
761
+ * - ``true``
762
+ - Path-style URL
763
+ - ``s3.amazonaws.com/<bucket>``
764
+
765
+ * - ``false``
766
+ - Virtual-host-style URL
767
+ - ``<bucket>.s3.amazonaws.com``
768
+
769
+ Default value is ``true``.
770
+
771
+ .. opsmgrkube:: spec.backup.s3OpLogStores.s3BucketEndpoint
772
+
773
+ *Type*: string
774
+
775
+ *Required to store the oplog using an S3 store.*
776
+
777
+ URL of the |aws| |s3| bucket or |s3|-compatible bucket that hosts the
778
+ oplog store.
779
+
780
+ .. opsmgrkube:: spec.backup.s3OpLogStores.s3BucketName
781
+
782
+ *Type*: string
783
+
784
+ *Required to store the oplog using an S3 store.*
785
+
786
+ Name of the |aws| |s3| bucket or |s3|-compatible bucket that hosts
787
+ the oplog store.
788
+
789
+ .. opsmgrkube:: spec.backup.s3Stores.irsaEnabled
790
+
791
+ *Type*: boolean
792
+
793
+ Flag that enables using |aws| :aws:`IAM roles for service accounts </eks/latest/userguide/iam-roles-for-service-accounts>`
794
+ in |aws| :aws:`EKS </eks/latest/userguide/what-is-eks>` to configure
795
+ an S3 snapshot store. The default is ``False``. If you aren't using
796
+ |aws| EKS, this flag has no effect. When set to ``False``, using |aws|
797
+ IAM roles for service accounts in EKS to configure an S3 snapshot
798
+ store is disabled. To learn more, see
799
+ :aws:`IAM roles for service accounts in EKS </eks/latest/userguide/iam-roles-for-service-accounts>`.
800
+
669
801
.. opsmgrkube:: spec.backup.s3Stores.name
670
802
671
803
*Type*: string
672
804
673
- *Required if you enable Backup using an S3 store.*
805
+ *Required to store the oplog using an S3 store.*
674
806
675
807
Name of the |s3| snapshot store.
676
808
0 commit comments