Thank you very much for your response. I will consider the feedback from the 
previous review and try to minimize the reviewer's workload as much as possible.

> On Mar 11, 2024, at 18:44, Masatake Iwasaki <[email protected]> wrote:
> 
> I think the only concern is bandwidth of developers/reviewers.
> While my first priority is moving 3.3 release forward now,
> we can work on the Knox without blocking the release.
> 
> 
>> Knox's proxy access capabilities provide an intuitive means for users to 
>> access the UI interface of Kerberos-enabled clusters.
> 
> The manifests of bigtop-deploy for deploying cluster with Kerberos has
> limited coverage and may be outdated since we usually run smoke-tests without 
> it.
> Additional effort should be needed for testing the Knox well.
> 
> Thanks,
> Masatake Iwasaki
> 
> On 2024/03/07 16:17, Jialiang Cai wrote:
>> Dear community members,
>> I trust this message finds you well. I am reaching out to initiate a 
>> thoughtful discussion regarding the ongoing support for Knox within the 
>> Bigtop open-source community.
>> It has come to my attention that a pull request (PR) was submitted in 2022 
>> by a  contributor, aiming to integrate Knox support. The significance of 
>> this effort lies in its ability to enhance Knox functionality, particularly 
>> in clusters employing Kerberos. Knox's proxy access capabilities provide an 
>> intuitive means for users to access the UI interface of Kerberos-enabled 
>> clusters.
>> Regrettably, the aforementioned PR appears to have been inactive, with no 
>> recent engagement from the original author. Despite attempts to reach out in 
>> August 2023, there has been no response.
>> Recognizing the importance of this feature and its potential benefits to the 
>> community, I am contemplating the creation of a new pull request to continue 
>> the integration of Knox support into Bigtop. This would ensure that the 
>> development remains dynamic and that the valuable contributions made by the 
>> community are not impeded by an inactive or departed contributor.
>> For your convenience, the link to the original PR is provided here: 
>> [https://github.com/apache/bigtop/pull/1029](https://github.com/apache/bigtop/pull/1029)
>> I would greatly appreciate any insights, suggestions, or feedback from the 
>> community on this matter. Your perspectives are invaluable in determining 
>> the most appropriate course of action to keep the project advancing.
>> Thank you for your time and consideration.
>> Best regards, jialiang

Reply via email to