Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version of gokrb5 once AD compatibility is solved #253

Closed
jankaspar opened this issue Nov 21, 2019 · 1 comment · Fixed by #312
Closed

Update version of gokrb5 once AD compatibility is solved #253

jankaspar opened this issue Nov 21, 2019 · 1 comment · Fixed by #312

Comments

@jankaspar
Copy link
Collaborator

We are using patched version of the library (jcmturner/gokrb5#278 (comment))

Once these prs are merged we should switch back to the original:
jcmturner/gokrb5#325
jcmturner/gokrb5#299

@jgiannuzzi
Copy link
Member

gokrb5 v8.1.0 now fixes those issues

jankaspar added a commit that referenced this issue Feb 18, 2020
jankaspar added a commit that referenced this issue Feb 19, 2020
svc-gh-ghzonetrans-p pushed a commit that referenced this issue Oct 17, 2024
* Move PulsarConfig into common/config (#217) (#3907)

* ARMADA-2848 Move PulsarConfig into commonconfig

* Update test name TestValidateHasJobSetID->Id

* Revert unintended changes to yarn.lock file

* fix import order

Co-authored-by: Eleanor Pratt <[email protected]>

(cherry picked from commit 35cb59f)
Signed-off-by: mustaily891 <[email protected]>

* Adding ControlPlaneEventsTopic to pulsar config

* Evolving ControlPlaneEvents message structure

We've decided on a parent/wrapper message for the ControlPlaneEvents to avoid passing around ambiguous proto.Message slices in the Publisher and Ingester.

* Setting maxAllowedMessageSize to correct value in relevant tests

* Removing reason for uncordon requests to the executor service

* Moving event creation time to parent Control Plane Event, modifying executor service rpcs to reflect the events being published, changed pulsar message keys to hard coded strings rather than proto name

* Renaming UpdateExecutorSettings rpc to UpsertExecutorSettings

* Removing message keys from ControlPlaneEvent messages, reverting method name changes

* Renaming LimitEventSequencesByteSize

* Adding executor cordoning functionality to armadactl

* Renaming ControlPlaneEvent to Event

* Simplifying executor cordoning code

* More sane checks on UpsertExecutorSettings rpc, better error messages

* Typo

* Updated command descriptions for executor cordoning and uncordoning

* Separating executor service args from controlplaneevents

* Executor Service #2 (#254)

* Generalising common ingestion pipeline

* Removing unused config

* Amending comments and variable names in common ingestion pipeline to be more event agnostic

* Returning to original metric name, denoting ingested event type via labal rather than metric name

* Import ordering

* Generalising pulsar publisher

* Executor Service #3 (#255)

* Modifying SchedulerIngester to ingest control plane events, creating executor settings table and associated plumbing

* Simplifying dbops merge for controlplanevents

* Moving DBOperation scoping into schedulerdb

* Adding GetOperation method to DBOperation, determining locking using this

* Executor Service #4 (#257)

* Implementing cluster cordoning in scheduler

* Filter executors from previous filter result

* Adding default value for queue label when publishing controlplaneevent metrics

---------

Signed-off-by: mustaily891 <[email protected]>
Co-authored-by: Eleanor Pratt <[email protected]>
MustafaI added a commit that referenced this issue Oct 17, 2024
* Move PulsarConfig into common/config (#217) (#3907)

* ARMADA-2848 Move PulsarConfig into commonconfig

* Update test name TestValidateHasJobSetID->Id

* Revert unintended changes to yarn.lock file

* fix import order



(cherry picked from commit 35cb59f)


* Adding ControlPlaneEventsTopic to pulsar config

* Evolving ControlPlaneEvents message structure

We've decided on a parent/wrapper message for the ControlPlaneEvents to avoid passing around ambiguous proto.Message slices in the Publisher and Ingester.

* Setting maxAllowedMessageSize to correct value in relevant tests

* Removing reason for uncordon requests to the executor service

* Moving event creation time to parent Control Plane Event, modifying executor service rpcs to reflect the events being published, changed pulsar message keys to hard coded strings rather than proto name

* Renaming UpdateExecutorSettings rpc to UpsertExecutorSettings

* Removing message keys from ControlPlaneEvent messages, reverting method name changes

* Renaming LimitEventSequencesByteSize

* Adding executor cordoning functionality to armadactl

* Renaming ControlPlaneEvent to Event

* Simplifying executor cordoning code

* More sane checks on UpsertExecutorSettings rpc, better error messages

* Typo

* Updated command descriptions for executor cordoning and uncordoning

* Separating executor service args from controlplaneevents

* Executor Service #2 (#254)

* Generalising common ingestion pipeline

* Removing unused config

* Amending comments and variable names in common ingestion pipeline to be more event agnostic

* Returning to original metric name, denoting ingested event type via labal rather than metric name

* Import ordering

* Generalising pulsar publisher

* Executor Service #3 (#255)

* Modifying SchedulerIngester to ingest control plane events, creating executor settings table and associated plumbing

* Simplifying dbops merge for controlplanevents

* Moving DBOperation scoping into schedulerdb

* Adding GetOperation method to DBOperation, determining locking using this

* Executor Service #4 (#257)

* Implementing cluster cordoning in scheduler

* Filter executors from previous filter result

* Adding default value for queue label when publishing controlplaneevent metrics

---------

Signed-off-by: mustaily891 <[email protected]>
Co-authored-by: Mustafa Ilyas <[email protected]>
Co-authored-by: Eleanor Pratt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants