Sergey
My feedback
72 results found
-
3 votesSergey
supported this idea
·
-
8 votesSergey
supported this idea
·
-
12 votesSergey
supported this idea
·
-
19 votesSergey
supported this idea
·
-
23 votesSergey
supported this idea
·
-
16 votesSergey
supported this idea
·
-
25 votesSergey
supported this idea
·
-
1 vote
An error occurred while saving the comment -
6 votesunder review · 2 comments · Ops Tools » Enterprise Kubernetes Operator · Flag idea as inappropriate… · Admin →Sergey
supported this idea
·
-
1 voteSergey
shared this idea
·
-
49 votesSergey
supported this idea
·
-
5 votes
An error occurred while saving the comment Sergey
commented
we've done such transition successfully recently. you need provide more details why it stuck... and probably open ticket with mongo support.
-
2 votes
An error occurred while saving the comment Sergey
commented
according to mongo support team, you can specify multiple comma separated hosts here. or you can "the most frequently used or used for queryable snapshots" kmip server here and configure different kmip servers in deployement page. But neither GUI nor documentation is clear about it...
both GUI and doco should be improved.
-
13 votesSergey
supported this idea
·
-
9 votes
An error occurred while saving the comment Sergey
commented
there is a similar issue when automation agent tries to connect as SCRAM-SHA-1 even if it's disabled and fails. I will add it here to group all authentication issues for automation agent.
```Testing auth with username __system db=local to ***:27017 (local=false) connectMode=SingleConnect ipversion=0 tls=true
[2021-09-09T10:25:22.801+1000] [.info] [cm/mongoclientservice/mongoclientservice.go:func1:1603] [10:25:22.801] Returning false for checkAuth on connParams=***:27017 (local=false) because we believe err is an auth failed error err=connection() : auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-1": (AuthenticationFailed) Authentication failed. (topology.ConnectionError)
[2021-09-09T10:25:22.801+1000] [.info] [cm/mongoctl/processctl.go:GetKeyHashes:1881] <RS_***_3> [10:25:22.801] Unable to successfully auth to ***:27017 (local=false) using desired auth key2021-09-08T23:11:51.625+1000 I ACCESS [conn1967736] SASL SCRAM-SHA-1 authentication failed for __system on local from client ***:50742 ; AuthenticationFailed: ###
```Sergey
supported this idea
·
-
2 votesSergey
shared this idea
·
-
3 votesSergey
shared this idea
·
-
17 votesSergey
supported this idea
·
-
1 voteSergey
shared this idea
·
-
5 votesSergey
supported this idea
·
An error occurred while saving the comment Sergey
commented
there is a special alert to notify customer when expiry date is less than 30 days.
But... this threshold must be configurable. for some organizations alert should be raised 60/90 days instead.
if it's configurable we can change threshold and get all about to expiry certs.
And I hope it will cover all types of certs - intra-node, agents.
is that what are you looking for:
...
podTemplate:
metadata:
labels:
network-role: mongodb
team: team1
tier: dev
spec:
nodeSelector:
deeming: SEC
component: mongodb-only
tolerations:
- effect: NoSchedule
key: mongodb
operator: Equal
value: SEC
- effect: NoSchedule
key: deeming
operator: Equal
value: SEC
- effect: NoSchedule
key: subnet
operator: Equal
value: NEW
...