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

merge conduit into linkerd as linkerd 2.0 #2018

wmorgan opened this Issue Jun 26, 2018 · 1 comment


None yet
3 participants

wmorgan commented Jun 26, 2018

(As discussed on the Linkerd maintainers mailing list)

This is a tracking ticket for merging Conduit ( into the Linkerd org, as the basis of Linkerd 2.0.

cc @adleong @olix0r @rmars @Ashald @zackangelo @ccmtaylor

@olix0r olix0r self-assigned this Jun 26, 2018

@adleong adleong added this to Short-Term in Linkerd Roadmap Jul 3, 2018

rmars added a commit to linkerd/linkerd2 that referenced this issue Jul 5, 2018

Start removing references to conduit in the web UI (#1260)
This PR starts removing all references to the word "Conduit" in the web UI.
In the interest of not making huge changes all at once, I'll gradually start moving away
from the usage of "conduit" in the Web UI. For example, there are a lot of components that
have conduit in their names but they don't need to.

This branch is mostly component / variable names. There should be no visible changes except 
the spinner is no longer a Conduit spinner.

See #1262 for visible branding changes.

- Rename ConduitLink to PrefixedLink
- Remove ConduitSpinner in favour of antd.Spin
- Remove css classnames that are conduit- centered
- Parameterize the current Product Name so that it's easier to change in the future

Tracking ticket: linkerd/linkerd#2018

This comment has been minimized.


olix0r commented Jul 10, 2018

The conduit repo has been moved to linkerd/linkerd2. The linkerd2-proxy repo has been split out, containing the rust proxy; and the linkerd2-proxy-api repo has been split out containing only the gRPC bindings (and related utilities) needed by the proxy and core projects.

Once basic docs (README, etc) have been restored and the proper access groups have been established, the repos will be unlocked. The linkerd2 repo still needs a fair amount of work before Linkerd 2.0-RC1 can be released.

@adleong adleong closed this Oct 4, 2018

@adleong adleong removed this from Short-Term in Linkerd Roadmap Oct 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment